rfletche
Active Member
Hi
Currently we have a set of Central Objects stored in SQL Server on the
Deployment Server and a second set on the Enterprise Server. The theory
was to decommission the SQL set and just use the AS400 set but package
builds take 3 days to eventually fall over with a memory violation.
So today, we pointed the CRP Pathcode to CRP Central Objects on SQL when
signed on to the JDEPLAN environment. The ESU worked fine as did a
package built from the DEPB733 environment. But the ESU didn't fix the
application bug. I changed the CRP pathcode to Central Objects on SQL
from my Client workstation and was able to check out the corrected
object. This could be broken by deploying the fix package made from the
DEPB733 environment.
So it appears that JDEPLAN uses Pathcode Master in its Access mdb but
DEPB733 like every other environment uses the one in System.
This is quite important to us as we may end up with a set of package
build environments ( with CO on SQL ) and a set of run time environments
( with CO on the AS400 ) and maintenance overhead for version RDA specs.
Any comments?
regards
Robert Fletcher
DHL
AS400 V4R4, 7332 SP15.1, Citrix & JAS.
Currently we have a set of Central Objects stored in SQL Server on the
Deployment Server and a second set on the Enterprise Server. The theory
was to decommission the SQL set and just use the AS400 set but package
builds take 3 days to eventually fall over with a memory violation.
So today, we pointed the CRP Pathcode to CRP Central Objects on SQL when
signed on to the JDEPLAN environment. The ESU worked fine as did a
package built from the DEPB733 environment. But the ESU didn't fix the
application bug. I changed the CRP pathcode to Central Objects on SQL
from my Client workstation and was able to check out the corrected
object. This could be broken by deploying the fix package made from the
DEPB733 environment.
So it appears that JDEPLAN uses Pathcode Master in its Access mdb but
DEPB733 like every other environment uses the one in System.
This is quite important to us as we may end up with a set of package
build environments ( with CO on SQL ) and a set of run time environments
( with CO on the AS400 ) and maintenance overhead for version RDA specs.
Any comments?
regards
Robert Fletcher
DHL
AS400 V4R4, 7332 SP15.1, Citrix & JAS.