gerd_renz3
VIP Member
RES: Deployment Server/Developer\'s workstation
Carl,
I have always appreciated your valuable contributions to the LIST and
learned a lot from them. However, this time I disagree on some of your
points. Let me explain, point by point.( I hope you don't mind. )
1.
"CARL: You can log onto the Deployment Server in any environment, it after
all has the only full set of Specs and DLLs for every environment."
Gerd: Yes, you can log into any environment on the deployment server, but
you are NOT executing a full set of specs when you log in any environment
different from JDEPLAN or DEP7333. All \B7333\PATHCODE\spec directories have
a reduced set of specs equivalent to a partial package. You note that when
you log into, let's say, PY7333 on the DS you get JITI for every program you
enter the first time. You can also compare the file sizes for the TAM files
with the ones from a full package. When you build a full package you cannot
deploy it to the deployment server itself, it's just not possible. So your
\B7333\PATHCODE\spec directory never gets updated, unless you do it manually
(copy-paste). The same is
Carl,
I have always appreciated your valuable contributions to the LIST and
learned a lot from them. However, this time I disagree on some of your
points. Let me explain, point by point.( I hope you don't mind. )
1.
"CARL: You can log onto the Deployment Server in any environment, it after
all has the only full set of Specs and DLLs for every environment."
Gerd: Yes, you can log into any environment on the deployment server, but
you are NOT executing a full set of specs when you log in any environment
different from JDEPLAN or DEP7333. All \B7333\PATHCODE\spec directories have
a reduced set of specs equivalent to a partial package. You note that when
you log into, let's say, PY7333 on the DS you get JITI for every program you
enter the first time. You can also compare the file sizes for the TAM files
with the ones from a full package. When you build a full package you cannot
deploy it to the deployment server itself, it's just not possible. So your
\B7333\PATHCODE\spec directory never gets updated, unless you do it manually
(copy-paste). The same is