*OW UBE not running on server*

Toni_Nanneman

Active Member
OW B7322 sp12.2; 400 ent srvr; NT depl srvr; SQL 6.5; coexist A73 cum8

OK, I've already kind of mentioned that I'm having a problem with a UBE that
was transferred with a version from CRP to PROD. The UBE's run fine locally
in PROD but won't run on the server. The UBE runs in all locations in CRP.

I've been hashing out this issue with JDE for over a week and they're latest
suggestion is to update the data dictionary TAM files on the Enterprise
server using the HowTo instructions from document oti-99-0023. Basically,
I'm supposed to run R92TAM (xjde0001) locally and then run tamftp and move
the dddict and ddtest spec files to the PRODB732/specfile directory on the
AS/400.

Finally, my question...

Has anyone ever done this before? Are there any major issues to be
concerned about? It seems fairly innocuous but I'm still a little bit
worried about wiping out the spec files on our 400. Any suggestions and/or
shared experiences would be GREATLY appreciated.


Toni Nanneman
CNC Administrator
503-370-7071 x7262
[email protected]
 
Hi Toni
We have completed this procedure a few times when specific ddtext or
related changes occur in OneWorld and don't seem to get to the server. I
would offer the recommendation that you trial the process in CRP, even
though your report runs fine on the server in that environ., and see that
the end result is still a fully functional CRP. Copy the existing IFS files
before replacing them.
If all is cool, then do the production change.
Sheena Bamsey
AS400 ES V4R4, B7331 SP 7.1, NT Deployment
SQL 7.1, Coexist A7.3 Cum 11
 
OW B7332 sp 11.3; ES 400 830 V4R5; DS NT 4.0 SP 5; CO SQL 7.0

Toni,

I do this every time I deploy a package to my ES. I actually TAMFTP to the
package subdirectory, then deploy, but have never had a problem.

Tom Davidosn



I've been hashing out this issue with JDE for over a week and they're
latest
suggestion is to update the data dictionary TAM files on the Enterprise
server using the HowTo instructions from document oti-99-0023. Basically,
I'm supposed to run R92TAM (xjde0001) locally and then run tamftp and move
the dddict and ddtest spec files to the PRODB732/specfile directory on the

Has anyone ever done this before? Are there any major issues to be
concerned about? It seems fairly innocuous but I'm still a little bit
worried about wiping out the spec files on our 400. Any suggestions and/or
shared experiences would be GREATLY appreciated.








OW 7332 SP 11.3VER, NT 4.0 SP 5, TSE 4.0 SP 4, Metrframe 1.8, CO SQL 7.0
 
Re: RE: *OW UBE not running on server*

I agree with Sheena. I always copy the specs to save directory before i run the tamftp (even though I've never used the saved specs).
dave

NT 4.0 SP5, SQL 7.0, One World B7321 SP12.4, Citrix
 
RE: RE: *OW UBE not running on server*

Thanks to those of you who advised running the TAMFTP in an alternate
environment and saving the specs before running! It saved my bacon today!
I tested running the TAMFTP to our DEV environment and afterwards every
custom UBE failed to run on the server. I replaced the saved specs in the
specfile and everything was back to normal.

My original problem is that when I transfer UBE's to PROD from CRP they will
not run on the server only locally.

So now I'm back to square one and under a major time crunch with some new
Year End UBE's I need to run in PROD. Any other suggestions for fixing the
problem with running UBE's on our enterprise server? I'm still waiting to
hear back from JDE!

B7322 sp12.2; coexist World A73 cum8; 400 ent server; NT Depl server with
SQL 6.5

Toni Nanneman
Holiday Retirement Corp.
 
RE: RE: *OW UBE not running on server*

Hi,

For us, we TAMFTP to a new directory we created ourselves on the ES. When
everyone is off the system, we will down the OneWorld services and just do a
unix copy to copy the new specs to the production specs. We've not had any
problems with that.

Sook Fun
B7322 SP12.2, HP-UX, Oracle
 
RE: RE: *OW UBE not running on server*

Toni,
I had a similar issue last week. A UBE ran locally under CRP but
when transferred to PROD or DEV would not. In my case the Object Transfer
seemed to cause the problem. I ended up deleting the UBE from PROD then
using the Check In/Out to move it from CRP to PROD and finally used the
Object Transfer to move the Version only from CRP to Prod. I followed the
same steps to move it from CRP to DEV and now it runs from any environment
..


Paul Gaynor
B7322, NT DEP, NT ENT, SQL 7.0
 
Back
Top