One of the things that baan does well is keep a fifo list for accessing the vrc packages. When a session is required, it searches the list in lifo sequence lifo, until it finds the session in question, or returns a session not found.

My question is this: Why cannot baan keep the directories and all the subdirectories by vrc, out of the search path, and allow me to build a single level directory set for a package combination? (do a rollup to one and only one directory), with the other directories around for maintenance or rebuilding?

My vrc structure would then be kept individual directories, and in one directory, all the sessions and objects pertaining to a session would be copied.

Now, instead of searching many many directories, until standard is found, we search only one level.

In the old days, disk space was $$$. That is no longer the case.

For patches and development environments, we could do our testing in easy ways too.

Consider this situation (for baan4 as example) we have
stnd-->localization-->sp1--sp2-->sp3-->... sp10-->customization.

I would have only one level "production", which is the merge of customization, all the sp's localizations and base.

test would be the copy of customization to a test directory, and therein, the new items to be tested.

Any comments?

Leslie

One thing I appreciate in Baan is the easy and fast structure that is used for the RTDD.

When I run a session with quite debug info I notice that most of the time spent is the DD load and query of data in the database, mostly with sessions that access tables with a huuge nr. of rows.

And the OS delays are nothing compared with the network load delays... I don't think a change at OS level structure will improve performance.

Mr. Leslie,

Your ideas are worth a discussion. But I cannot completely understand your thoughts. You're discussing sessions and the way they are searched.
I think there is some confusion here: RT information of sessions is stored in a table keyed on pacc and session code: so there is a copy of this record in every pacc.

Since you are talking about directory searches, I assume you meant objects. Is this correct?

You're idea is then to copy the objects to every possible pvrc to fill in the holes. The disadvantage of this would be that delivering a patch (or update/customization) would be a horrible job, just because it has to be copied to every possible pacc. If you work with SCM (typical in a development environment), you would have to make copies to lots of directories and synchronize lots of times.

Before i continue; am i correct? is this the direction you want the discussion to go?

Regards,
Jaap Zwaan

Leslie,

Yes it is possible that you can sort different package VRC's into different directories and we can then do some scanning, disk space sizing etc on those directories. So we have less subdirectories in our $BSE/application directory and its easy to go into the relevant directories and do some processing.

We use this feature already. Please look at the screen shot.


>ll
total 20
drwxr-xr-x 55 bsp bsp 2048 Sep 24 10:24 baan
drwxr-xr-x 2 bsp bsp 96 Sep 4 15:23 ccB50_a_in01
drwxr-xr-x 2 bsp bsp 96 Sep 4 15:23 da7.1_a
drwxr-xr-x 2 bsp bsp 96 Sep 4 15:23 dcB50_a_98
drwxr-xr-x 2 bsp bsp 96 Sep 4 15:23 dt7.3_a
drwxr-xr-x 29 bsp bsp 4096 Nov 5 10:14 ibaan
drwxrwxr-x 128 bsp bsp 4096 Nov 4 01:40 baseline
drwxr-xr-x 2 bsp bsp 96 Sep 4 15:23 pf7.0_a1
drwxr-xr-x 2 bsp bsp 96 Sep 4 15:23 spB50_b_reg
drwxr-xr-x 2 bsp bsp 96 Sep 4 15:23 wdB50_a_2
drwxr-xr-x 2 bsp bsp 96 Sep 4 15:23 xxB50O_c_ptg


If this isnt what you are looking for please explain it explicitly.