gerd_renz3
VIP Member
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
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