Versions List

Hi List,
I have a client with a somewhat peculiar setup. They have six different
sets of Production Business Data and accordingly six different production
environments. All share the same Pathcode PD7333.
The question came up, how can each environment have it´s own set of
versions? We copied the PD7333.F983051 versions header table to each
Business Data and created the OCMs accordingly. The existing versions
appear and can be used. However, when we create new versions (copy an
existing one), independent from which Environment I am logged in, it will
always be created in the same F983051.
Example: I have Env1 - Env6, with Business_Data1 - Business_Data6 with a
copy of F983051 in each of them, with correct OCMs. When I create a new
Versions, it will always be registered in Business Data1, no matter which
of the 6 Environments I am in.
I already found out from a trace file, that OW does this:
It lists all Environments with my PATHCD in alphabetical order,

SELECT LMLL FROM SYS7333.F00941 WHERE ( LMPATHCD = 'PD7333' ) ORDER BY
LMLL ASC

It then finds the OCM for F983051 and the FIRST environment in this list

SELECT OMDATP, OMSTSO FROM SYS7333.F986101 WHERE ( OMENHV
= 'CASASHOP ' AND OMOBNM = 'F983051' AND OMUGRP = '*PUBLIC' )

That´s why the version is always created in the same Datasource, no
matter what environment.

Is there any way around this so my client can have private versions for
each environment?

Thanks, Gerd
Xe, SP16, Update6, W2K, SQL Server, WTS


********Confidencialidade do Correio do Eletrônico

Gerd,


It would be a dicey move, but you could try copying and remapping the F00941
to the Business Data - X data sources. After the coping is completed,
remove the other production environments. This would have to be done for
each production environment. I would then create another map for the
OneWorld Admin group that points back to the original table in the SYS7333
Database.

In theory, the users from ENV1 would only know about ENV1, ENV2 users would
only know about ENV2, etc... The only group that would see all of them
would be the OneWorld Administrators.


Hope this works out for you.








Consultant with clients
at B7331 - Xe
Various Deployment Servers, Citrix and JAS

Hi Gerd,

I think we have similar situation. We created a "dummy" environment that
would be the first one alphabetically, and after the version gets created
there we simply copy it to the environment it belongs to.

Dave Schleicher
Senior Support Analyst
LOGIS
B733.2
SP 17.1
Oracle
NT Servers
Citrix users

Hi,
We are in the same position with 4 production environments using the PD7333 path code. The way we do this is to have a naming convertion where all Westcon Unites States versions start WUSxxxxx.

You can then apply row security on Version in the F983051 to stop the other companies seing the other versions. It works absolutely fine and saves:
a) Having duplicate tables.
b) Making unescessary OCM mappings.

Any more info let me know.