TRITON 3.1 Staged Plan for the Update of TRITON 3.1 to ...

TRITON 3.1

Staged Plan for the Update of TRITON 3.1to TRITON 3.1b5

Installation Manual U7091A US

Staged Plan for the Update of TRITON 3.1 to TRITON 3.1b5


Document information

Document

Document code : U7091A USDocument group : User DocumentationDocument title : Staged Plan for the Update of TRITON 3.1 to TRITON 3.1b5Edition : AMonth modified : November 1997

Check the BaanDoc database to see if this document is still a valid edition.

© Copyright 1997 Baan Development B.V. All rights reserved

The information in this document is subject to change without notice. No part of this document may

be reproduced, stored or transmitted in any form or by any means, electronic or mechanical, for any

purpose, without the express written permission of Baan Development B.V.

Baan Development B.V. assumes no liability for any damages incurred, directly or indirectly, from

any errors, omissions or discrepancies between the software and the information contained in this

document.

Staged Plan for the Update of TRITON 3.1 to TRITON 3.1b5i

Table of contents

1. Preparation 11.1 Backup 11.2 TRITON 11.3 System manager 11.4 Time frame 21.5 Prerequisites 21.6 Disk space 2

2. Installation procedure 52.1 Step 1: reading out tapes 52.1.1 Regular tape 52.1.2 Master tape 52.1.3 Tape with customizations 62.2 Step 2: start the installation script 62.3 Step 3: check the installation logs 72.4 Step 4: B/C-VRCs–import customization 72.5 Step 5: create new VRCs (ttadv1111m000) 72.6 Step 6: create directories for new VRCs 82.7 Step 7: O-VRCs–copying own work to new own VRCs 92.8 Step 8: create new package combinations 92.9 Step 9: fill package combinations with VRCs 92.10 Step 10: migrate companies 102.11 Step 11: migrate users 102.12 Step 12: check bug fixes in U-VRCs 102.13 Step 13: O-VRCs–dump forms and menus 112.14 Step 14: O-VRCs–compile reports 122.15 Step 15: patching 122.16 Step 16: create tables 122.17 Step 17: parameters 122.18 Step 18: correction objects 132.19 Step 19: create runtime help 132.20 Step 20: checking and finalizing 14

Staged Plan for the Update of TRITON 3.1 to TRITON 3.1b5ii

Staged Plan for the Update of TRITON 3.1 to TRITON 3.1b5iii

About this document

This document describes the update of TRITON 3.1 to TRITON 3.1b5.

Chapter 1 describes the preconditions for the update.

Chapter 2 describes the steps of the update.

This document can be used by all persons that want to update a TRITON 3.1environment to a TRITON 3.1b5 environment on a UNIX server. However, usersmust have an elementary knowledge of UNIX. Users must also have an elementaryunderstanding of the way TRITON software is structured: with Package VRCs,Package Combinations, and the derived-from structure.

The person performing the update must also know something about how to movearound in TRITON 3.1, that is, what keys to use to perform certain actions. A fewhints are given below.

The document describes an update of TRITON 3.1 on a (single) UNIX server. Theexamples and descriptions of actions on the UNIX prompt presuppose the use of theKorn shell (ksh). In the text, the user is supposed to use an ASCII interface, whichactivates an user session through the ba6.1 command. This of course can also be an XWindows interface if X is configured on the server (bx6.1).

There are four possible types of databases:

1 tbase2 tbase_tp3 Oracle4 Informix

However, the update is (in principle) fully transparent to your database type.

The following points about notation should be noted:

n Keystrokes are placed between brackets.Angle brackets for function keys. Square brackets are used for letters andtypographic characters.

For example:− Press <Ctrl>[C]− Use the <Shift> key− Use [C] to edit the screen

n UNIX keywords, variables, path names, and so on are in bold (case-sensitive).

For example:− The cpio command− Use licmon5.0 -b− Go to $BSE/bin

Staged Plan for the Update of TRITON 3.1 to TRITON 3.1b5iv

n Variables are in italics.

For example, create the directory path name/baan. This asks you to create asubdirectory baan somewhere in the file system, for example, /usr3/baan or/disk1/temp/baan.

The following hints give some guidance on how to use the interface:

n To exit of a field and return to the Choice prompt, move the cursor to the first left-hand position of the field and press <Esc>.

n Type [E] at the Choice prompt to leave a session while keeping the changes. Type[A] to leave without making changes.

n The Choice prompt is language-sensitive. This means that you press [Y] for Yes inEnglish, [J] for Dutch and German, or [O] for French, and so on.

n Type [O] at the Choice prompt to view your options. Press <F6> to display apopup menu. Press <Esc> to leave the menu without selecting anything.

Preparation


1.1 Backup

You require a good and recent backup of the software and the tables present, inparticular of the tools and company tables that you want to migrate to TRITON 3.1b5.

1.2 TRITON

You cannot use TRITON while the installation script is running. Nor can you usecompany numbers that are being reconfigured when they are migrated from onepackage combination to another, or while the operational package combinations thesecompany numbers are associated with are being dumped.

Complications can arise from bug fixes that have been installed in the TRITON 3.1_aor TRITON 3.1_b environment. If these bug fixes have been installed in the3.1U_a_stnd or 3.1U_b(2)_stnd VRCs (which are intended for these bug fixes), theycan be screened and, if necessary, copied to the TRITON 3.1_b5 environment. Seestep 12 in the procedure.

This is, of course, impossible, if these 3.1U_xx_stnd VRCs are not present, and bugfixes have been installed in the standard VRCs. In this case, you must determinewhich bug fixes have been installed, and which of these are not included in theTRITON 3.1_b5 update. The ones that are not included in the TRITON 3.1_b5 update,must then be obtained and later on placed in the 3.1U_b5_stnd VRCs. To determinewhich objects these are, check your bug fix administration, or call the BSC.

In case of an update of TRITON 3.1_a to TRITON 3.1_b5, checking the bug fixesmust be done before the update-installation script is run because this is a full updateand the overwrite option is set to Yes. Otherwise, there is a chance some bug fixes willbe lost if they are located in TRITON 3.1_a VRCs. Please note that in this case, whenbug fixes in the TRITON 3.1_a VRCs are overwritten during the update, they will alsobe lost for the TRITON 3.1_a operational environment(s).

If no bug fix administration exists, that includes a registration of the bug fixes anddetails of where they are installed, you must perform the update and obtain the lostbug fixes afterwards –when old errors recur– from the backup (see section 1.1).

1.3 System manager

If installing the update with the help of BAAN, the customer’s system manager musthelp with, for example, reading tapes, make it possible to call in by modem, and startthe installation script.

1. Preparation

Preparation


1.4 Time frame

The time frame of the update very much depends on the system and the database type.Assuming the installation script is started on the evening of the first day, allow 4 to 8hours on the second day to complete the job. This may be considerably more –to thepoint of having to allow a third day– where Oracle installations and/or the conversionof many or large companies are involved. The time frame on the first day is 1 to 5hours to read out the tape(s); a master tape takes longer than a regular installationtape. Allow an additional half hour to prepare the update and to discuss the procedureof how to install the update with a technical specialist of the Baan Company. Take intoaccount that you may want to run a backup first. The installation script takes between1 and 5 hours (in case of updates with the Oracle database it can take more time) torun.

1.5 Prerequisites

Reserve 300 MB to 500 MB for reading the tape. A full standard update (full update)requires 150 to over 250 MB (for one language, excluding customization, underbisam), distributed as follows:

n Approximately 100 MB for the 3.1b(5) VRCs ($BSE/application).

n 50 MB for the new porting set (the old $BSE/bin is copied; may be removed later)

n Some expansion of the tools tables ($BSE/dict; or Oracle or Informix’s .dat and.idx space. Remember that the ratio between bisam and Oracle is about 2.5: 50 MBin bisam is equivalent to 125 to 150 MB in Oracle)

Allow an extra 200 MB per additional language.

1.6 Disk space

Log on to the system to see if there is sufficient disk space in the right places (seeprevious section).

Check the packages installed. Use (du -s $BSE/application/*) to determine theminimum required space. Only installed packages are updated (having tp installedmakes a 100 MB difference, in addition to possibly 10 MB of localizations).

Check the derived-from structure, the package combinations, and associatedcompanies.

After installation, the existing TRITON 3.1_a or TRITON 3.1_b structure that willcontinue to be used must be copied, as it were, under TRITON 3.1b5. This requiresthe creation of at least one new (TRITON 3.1b5) package combination.TheTRITON 3.1b5 environment must be set up for testing; this implies that you shouldnot at this stage migrate all existing package combinations (and associated companynumbers) to TRITON 3.1b5! As a rule, only those TRITON 3.1b5 equivalents of thepackage combinations that have companies attached to them (but do not create anequivalent of the standard [31Sb or 31Sb5] package combination) must be created.

Preparation


If the Baan Company installs the software, make sure that, does the installation a(physical) conversion of the company’s own customizations (O-VRCs) toTRITON 3.1b5, is included. Note that the adaptation of forms, menus, reports, and soon is the responsibility of the owner of the customizations.

Take into account any (new) customizations, too. If there is customized software inTRITON 3.1a or TRITON 3.1_b, the customization supplier must update this toTRITON 3.1b5. This applies to B, C, and possibly L-VRCs, when these are notincluded on the (master) tape. The update cannot take place before the updatedcustomized software has been delivered on tape.

Generally, one single company and a number of users are migrated to each newpackage combination for testing purposes and, possibly, for changes in own softwareby the customer.

Make a list of the package combinations for which a TRITON 3.1b5 version must becreated (and what each one will be called).

Finally, discuss everything.

This means:

n The backupn TRITON downtime/time framen Task assignmentn Configuration after the update (package combination(s), user(s) and

company/companies to be migrated).

You must only deviate from the test scenario if the risks that going live with theupdate involves have been carefully explained to you and if you are prepared to takeon those risks.

Remarks

n For Motorola and Hewlett Packard with short file names, the mechanism describedabove (when the porting set is replaced, the old bin files are copied to their originalname followed by a dash (-)) does not work: the 15-character limit is exceeded,which causes the installation script to block.

n This can be prevented as follows (instead of rc.stop and rc.start in step 2 of theinstallation procedure):

− Stop TRITON.− Move the directory $BSE/bin to, say, $BSE/save/bin.− Copy the bin directory from the tape directory (under ln.0000/bse/bin) to

$BSE/bin.− Move the contents of the bin directory from the tape directory to another

directory (not under the tape directory; for example,usr3/baantape/ln.0000/bse/bin to /usr3/save/bin). The directoryln.0000/bse/bin should be retained, but empty. Copy the new porting set(coming from the tape) to the directory $BSE/bin before the installation scriptis started.

− Restart TRITON and continue, beginning at step 2 of the installation procedure.

Preparation


Installation procedure


2.1 Step 1: reading out tapes

There will always be at least one tape available for the update: a regular tape (for BaanCompany (NL) customers) or a master tape. This tape contains the standard softwareand, possibly, localizations (L-VRCs).

Finally, customized software (C-VRCs) or line-of-business specific software(B-VRCs) can be available on another tape.

Make sure all the required tapes, containing standard software and customizations, areavailable.

2.1.1 Regular tape

Create a temporary, empty directory (for example, path name/baan) on a suitable filesystem. Do not include a directory or subdirectory with the name bse5.0 in the pathname.

In this empty directory, read out the tape by typing the cpio command or the bstapeutility.

Use cpio -itcdvB to list the contents, use cpio -icvdB to read (with or without v forverbose). 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 to list the contents, use bstape off to read(no background; verbose).

2.1.2 Master tape

Detailed information about reading out mastertapes is provided in the TRITON 3.1Installation Manual (5574US), under the section 6574-04US, Loading the Software orin the Reading the Master tape for Tools version 5.0, and 6.1 (U7003A US) manual.

Create a temporary, empty directory (for example, path name/baan) on a suitable filesystem. Do not include bse5.0 in the path name. In this empty directory, read the firstblock from the master tape or the whole regular tape.

Type cpio -itcdvB for a contents listing, type cpio -icvdB for a reading (with orwithout v for verbose) of the regular tape. Use the default no-rewind device (with nohardware compression).

Start the masread6.1 script by entering ./masread6.1, while you are in the directorywhere which you read out the tape.

Select the package VRCs and languages to be installed. Baan can provide a listing ofthe software to determine what these are.

Subsequently, the script will read these elements from the tape.

2. Installation procedure

NOTE:



2.1.3 Tape with customizations

Read each tape in a new, empty directory using the procedure for a regular tape,unless the instructions with the tape give other directions.

2.2 Step 2: start the installation script

User must be root!

While the installation is running, you cannot use this environment. Check if everyonehas left the bshell and has been advised (by the system manager) that TRITON cannotbe started. Log on with the user root (do not use the su command). Check your TERMvariable (echo $TERM). The vt220 emulation cannot be used: preferably use vt100instead. First, run the rc.stop. Next, run the rc.start script to remove any hungprocesses and database locks. If rc.stop fails, bring down the environment manually.

If Baan is installing the update by modem, the maslat utility will be used to start theinstallation, if possible. In this way, the modem connection can be disconnected again.The modem is not occupied, and can be used for other purposes. Only with this utilitycan the installation run as a background process.

The installation uses the (path) data in $BSE/lib/install/install.data. It is advisable tocheck the data before installation.

Keep the TRITON 3.1B5 Release Information (5968US) ready.

Go to the installation directory and start the install6.1 script via ./install6.1. The scriptonly prompts for the $BSE directory. Enter the $BSE of the TRITON 3.1_a orTRITON 3.1_b(2) environment to be updated.

Languages or localizations cannot be selected for installation. In case of an update ofTRITON 3.1_a a standard (3.1Sb) package combination is created. If the previousinstalled version was TRITON 3.1_b(2); answer the question “Full update?” with No.If the previous installed version was TRITON 3.1_a, answer this question with Yes.

The installation script can be interrupted by entering an interrupt (for instance, bypressing <Esc> followed by [q]). After interruption, the script can simply be restarted.Press [!] to start a UNIX shell, and return to the installation script via exit. Themessage from the script that says “Please remove all running bshells, pdaemon etc.” ismisleading, in that you are not meant to interrupt the installation script and start killingprocesses manually (least of all the license daemon). The message is only meant toindicate that the installation script is doing this for you. The last question asked by thescript is: “Are you ready for installation?” Only after this is answered with Yes theupdate starts.

The installation script first calls ottiex1287, then starts reconfiguring the tools tables,and then calls ottiex1288. Under bisam, it takes approximately 30 minutes to reachthis point.

Once the installation script has reached ottiex1288, the rest of the installation willprobably run smoothly (unless confronted with disk space problems or power failure).



2.3 Step 3: check the installation logs

After installation, the installation directory should be empty.

When a regular tape is used, the directory extra remains.

Close maslat after using. The log files are in directory $BSE/log. Check the mostrecent ones (type ls -ltr $BSE/log to find them). Create a file called setbse in $BSEthat sets the BSE, BSE_TMP, PATH and TERM(=vt100) variables. If the installationhas been completed successfully, the users can start using TRITON again.

2.4 Step 4: B/C-VRCs–import customization

From here on user must be logged on as bsp!

Import the customization dumps (when available) with the Import Customization(ttiex1285m000) session. Import the dumps in their original VRCs (so, do not renamethem).

If line-of-business specific software is available, follow the instructions for thatparticular type of software. See the document about Importing Software dumps (forC-VRCs), and for instance, the Installation TRITON Branchemodel document (forcertain types of B-VRCs).

2.5 Step 5: create new VRCs (ttadv1111m000)

From here on user must be logged on as bsp!

Create the O and U-VRCs using the Maintain Package VRCs (ttadv1111m000)session:

13 Application Development

3 Packages and Modules

3 Maintain Package VRCs

Create U-VRCs, derived from the standard 1.3b5/3.1b5/6.1b, for all packages (exceptge and tb) in the format: package code/3.1U/b5/stnd/Updates package name 3.1b5.

For example, tc/3.1U/b5/stnd/Updates Common 3.1b5.

If the localization 3.1L_b5_nl10 is included, then for tf and tp derive the U from the Linstead of from the standard.

Do not include the ti (Business Organizer - 3.1L_b5_org1) localization in the derived-from structure.

In the Business Organizer, items, for instance, are renamed as business objects.Therefore do not incorporate them in an operational, design or testing packagecombination. For those who want to use this localization, a separate packagecombination can be created.

In case of customizations (C-VRCs), derive the customization from the U-VRCs. If(also) B-VRCs are available, put these in the derived-from structure in the appropriateplace. See the documentation mentioned at the beginning of this step.



Create customer-specific VRCs for tc to ts (except tg and tu). Basically, copy theexisting structure of own VRCs to TRITON 3.1b5. Retain the existing customerextension(s) as much as possible.

Example:

OPER_001 contains 3.1O_b_kl01, derived from TRITON 3.1_b2. DSGN_001 contains3.1O_b_dsg1, derived from 3.1O_b_kl01. Now create two new series of own VRCs:3.1O_b5_kl01 (derived from 3.1U_b5_stnd, as no customization is involved) and:3.1O_b5_dsg1 (derived from 3.1O_b5_kl01).Check the derived-from structure via the Print Package VRCs (ttadv1411m000)session.

2.6 Step 6: create directories for new VRCs

Create directories for all new (U and O) VRCs using the Maintain SoftwareComponent Directories (ttadv1115m000) session:



4 Maintain Software Component Directories

Press [S] and enter the name of the VRC. Press [I] to enter the six software componenttypes. Do this for all VRCs.

If the components are entered in the order of the enum (press the spacebar), you canuse the TRITON copying facility:

n Enter the six components for the first VRCn Press <Esc> to go to the choice fieldn Press <Ctrl>[W], [Y], [B], [Y]n Enter the name of the next VRCn Press [Y]n Repeat these steps (from <Ctrl>[W] on) for all VRCs



2.7 Step 7: O-VRCs–copying own work to new own VRCs

Start the Copy Software Components to New Package VRC (ttadv6265m000) session:


16 Utilities

1 Copy Software Components to New Package VRC

For every own VRC, you have to copy all data within this VRC from the old to theproper new O-VRCs.

Run this session for VRCs that are empty at UNIX level. There may be domainsattached, or recent developments that are already present in tools may not have beenconverted to run time.

After this session, the new O-VRCs at UNIX level are still (largely) empty; copying iscurrently only done at the Tools level .

2.8 Step 8: create new package combinations

Call the Maintain Package Combinations (ttaad1120m000) session:

2 Application Configuration

8 Maintain Package Combinations

Create one or more new package combinations. Do not put these in shared memory.

2.9 Step 9: fill package combinations with VRCs

Start the Maintain Packages by Package Combination (ttaad1221m000) session:



6 Maintain Packages by Package Combination

Fill the new package combination(s) with the U (for tg and tu) and O (other) VRCs.Again, keep to the original structure, but leave out ge (General) and tb (TRITONSupport). End with [Y] to dump the package combination. Do this step for all newpackage combinations.

NOTE:



2.10 Step 10: migrate companies

Convert at least one company to each new package combination via the ChangePackage Combination by Company (ttaad1101m000) session:

2 Application Configuration

Press [→] twice, to reach the Miscellaneous menu.

2 Change Package Combination by Company

This session gives a list of warnings (of the type “Warning: No DD for tcedi472found”) as result. They relate to new tables (for which there is no DD inTRITON 3.1_a or TRITON 3.1_b but there is one in 3.1b5) and can be ignored. Whenin doubt, run the Check Tables session at the end of the procedure (see step 19 below).

2.11 Step 11: migrate users

Migrate at least one user (preferably at least bsp) to each new package combinationvia the Change Package Combination by User (ttaad2200m000) session:

3 User Management

1 General User Data

2 Change Package Combination by User

Convert this user data to run time using the Convert user data to a run-time datadictionary (ttaad4200m000) session.

Stop the bshell (and start it again in step 13, to activate the changes).

2.12 Step 12: check bug fixes in U-VRCs

There may already be U-VRCs in the TRITON 3.1_a or TRITON 3.1_b environment.If so, these have to be checked. It is possible that there are bug fixes (objects) such as3.1c objects in the 3.1U_a_stnd or 3.1U_b(2)_stnd VRCs that are not available in theTRITON 3.1b5 environment. These have to be copied to the 3.1U_b5_stnd VRCsmanually.

The procedure for doing this is completely at UNIX level.

First, using the what command, check the compilation dates of the objects in the3.1U_a_stnd or 3.1U_b(2)_stnd VRCs.

Then, using explode6.1, check in which VRC of the new package combination theseobjects are.

The explode6.1 tool uses the package combination as defined in the user file of theuser (in this case, bsp: $BSE/lib/user/ubsp). So, it is important to be attached to the(new) TRITON 3.1b5 package combination at this point.

Then check, using the what command, the compilation dates of these objects andcompare them to the dates of the objects in 3.1U_a_stnd or 3.1U_b(2)_stnd. If anyobjects in these VRCs are newer, copy them to the 3.1U_b5_stnd VRCs.

NOTE:



Keep in mind that, since these objects are newer, they are therefore supposed (!) to beTRITON 3.1_c objects, and not TRITON 3.1_b(2,3 or 4) objects. In most cases this isalso visible in the first line of the result of the what command (which shows thedirectory in which the source of the object is located on the development system).When in doubt, call the BSC.

The following is an example of a situation in which the oacp1120 object is checked,and the object in the 3.1_b5 VRC turns out to be newer than the one in the3.1U_b_stnd VRC (so it doesn’t have to be copied to the new 3.1U_b5 VRC).

sheliak> pwd/usr5/triton3/bse/application/tf3.1U_b_stnd/otfacpsheliak> lsoacp1110 oacp1120 oacp1133 oacp2121sheliak> what oacp1120 | head /d5/srcappl/tf3.1_b/ptfacp/pacp1120g, 95/11/27 [20:23], From bsp -DREL6_1 bic_global, 05-1993/R1, Copyright (c) Baan International b.v. bic_stdlib, 09-1992/R1, Copyright (c) Baan International b.v. bic_shell, 08-1994/R1, Copyright (c) Baan International b.v. bic_fork, 07-1992/R1, Copyright (c) Baan International b.v. bic_window, 04-1992/R1, Copyright (c) Baan International b.v. bic_process, 05-1992/R1, Copyright (c) Baan International b.v. bic_menu, 04-1992/R1, Copyright (c) Baan International b.v. bic_std, 01-1993/R1, Copyright (c) Baan International b.v.sheliak> explode6.1 otfacp1120/usr5/triton3/bse/application/tf3.1_b5/otfacp/oacp1120sheliak> what /usr5/triton3/bse/application/tf3.1_b5/otfacp/oacp1120 | head /d7/srcappl/tf3.1_b5/ptfacp/pacp1120g, 96/03/05 [16:07], From bsp -DREL6_1 bic_global 5.7:2/27/96 Copyright (c) Baan International b.v. bic_object 5.2:11/22/95 Copyright (c) Baan International b.v. bic_event, 04-1992/R1, Copyright (c) Baan International b.v. bic_shell, 08-1994/R1, Copyright (c) Baan International b.v. bic_fork 5.1:10/11/95 Copyright (c) Baan International b.v. bic_interface 5.8:2/16/96 Copyright (c) Baan Development b.v. ID 23053, Cor van Dijk, 1994-07-28, 3.0_b ID 23238, Cor van Dijk, 1994-09-22, 3.0_b

2.13 Step 13: O-VRCs–dump forms and menus

Start the bshell again. Use the Create Run-time Data Dictionary (forms and menus)(ttadv5214m000) session to convert the forms and menus associated with the migratedown work to runtime:


15 Run-time Data Dictionary

4 Create Run-time Data Dictionary (forms and menus)

Set the Dump field to 1 (default).



2.14 Step 14: O-VRCs–compile reports

Use the Compile Reports (ttadv3240m000) session to compile the reports associatedwith the migrated own work:


10 Reports

2 Compile Reports

Set the Compile field to 1 (default). During compilation an error report is generated.Check this report. All warnings can be very useful for the adaptation of forms, menus,reports, and so on. Note that the adaptation of the customizations is the responsibilityof the owner. If BAAN is installing the update for you, the installer will not checkthese warnings.

However, if there are any errors, check if the same errors occurred in the old version(by compiling the old own work via the old package combination, using the samesession). If the errors are identical in both versions, there is a problem with thefunctionality and the owner must be informed.

If there are no errors in the old environment (which is very unlikely), the problem islikely to have been created by the standard software or by the customization, and mustbe solved.

2.15 Step 15: patching

Check if there are any changes in the tools/software licenses. For this update alone, thekey need not be adjusted.

Use the Configure Application (ttiex3225m000) session from the Tools menu to patchthe software (provided the key need not be adjusted):

1 Software Installation

8 Configure Application

Fill out the fields as follows: Yes (; No;) Yes. Confirm with [Y]. When the messageSorting ... appears, the process is running properly.

2.16 Step 16: create tables

For all company numbers migrated to TRITON 3.1b5, create new empty tables usingthe Maintain Logical Tables (ttaad4230m000) session:

6 Database Management

Press [→] twice, to call the Miscellaneous menu.

3 Maintain Logical Tables

2.17 Step 17: parameters

Run the Parameters (tcmcs0295m000) session for all company numbers that weremigrated to TRITON 3.1b5.



2.18 Step 18: correction objects

Running the correction objects otfcor02273, otfcor0274, otfcor0275, and otfcor0266 ismandatory only for an update of TRITON 3.1_a to TRITON 3.1_b5. Run them for allcompany numbers that were migrated to TRITON 3.1b5. Press [P] and enter the tfobjects. A form is shown with the Update Table field and the Choice prompt. Theoptions for the Update Table field are:

n Y: execute and configure nown N: execute but do not configuren E: end sessionn ?: display session information.

For Choice, [Y] is the usual response. After execution, the cursor returns to the UpdateTable field. In case of errors, a Print Error Report screen is shown. Print the errors toan ASCII file. Inform the customer that there are errors and have the customer submita call (with reference to the error reports).

Submitting a call is no use for the demo companies (812 to 815 and 920): a number ofthese are liable to produce errors.

2.19 Step 19: create runtime help

Run the Create Runtime Help (ttadv5230m000) session for the entire environment(enter, for instance, tc - tz; 2.2O –2.2O; d-d; <space> - zzz; enable all check boxes ordefine all fields as Yes (ASCII)). You only need to run this session for the highestVRCs (the VRCs that are part of the package combination(s)).



2.20 Step 20: checking and finalizing

Make sure the scripts in $BSE/bin are restored to their old state (see the Remarkssection in Chapter 1, Preparation). In case of an update of a TRITON 3.1_aenvironment, objects that are loaded into shared memory (srdd_init) must be migratedfrom the old to the new tools version (from 6.1_a to 6.1_b). Use the following session:

2 Application configuration

6 Maintain Shared Memory Data (ttaad4150m000)

n Remove the old objects.n Enter the same objects, this time for 5.0_f.n Select Program Objects.n Press [I] to edit the screen.n Enter tt; the proper version is 5.0_f.n Enter an object from the list. Press <Enter> to fill out the next row.n Enter the entire list below:

Objects

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

n Press <Ctrl>[D] to run a conversion to run time.n If necessary, check the tables using session ttaad4232m000.n Test if the session tiitm0101m000 can be accessed in a company other than 000.n If ti is not implemented or Item Control is conducted via tp, use session

tccom1101m000 instead.

TRITON 3.1 Staged Plan for the Update of TRITON 3.1 to ...

Documents

Transcript of TRITON 3.1 Staged Plan for the Update of TRITON 3.1 to ...