DD, GLBL TBL and Package Build

pianosynth

Reputable Poster
We have had some recent problems occur in our AP which we think may be DD or GLBL TBL related. In working with JDE, we are getting some information regarding package builds that we think may be dubious at best. Can anyone shed some light on exactly what happens in a Full Package build? When the DD and GLBLTBL are built during a full package, where are the specs taken from for the build? ES, DS, Fat Client? If anyone knows this process completely and would be willing to take the time to share, it would be greatly appreciated.

B733.2, SP 15, Oracle 8.1.6, HP 9000
Win2K, Citrix 1.8, NFuse
 
They are not part of a build.

You can generate them and add them to the package before compression if you like, but, the default process is to allow these to jiti to the client and the server.

Dave.

David D. Helsley, Inc.
[email protected]
Xe, HPUX, Sp17.1, Oracle, TSE, Web
Xe, W2K, Sp17.1, MSSql, TSE
 
Have you refreshed the data dictionary and global table specs for your
Client and Servers? I often remember the clients but sometime forget the
servers. Just an idea.

B733.2 SP17.1_F1
Intel/NT/Oracle 8.1.7.1
 
Re: RE: DD, GLBL TBL and Package Build

DD and GLBLTBLs Can be rebuilt using R92TAM for DD and R98CRTGL for glbltbl. Alternatively you can rebuild only the DD and delete any glbltbl and let the server rebuild those itself (this is for enterprise or logic server, not Terminal Server)


OneWorld Xe Sp16_018, W2k, W2K TSE, SQL 2K on Compaq Proliant.
 
Hi

When I build a Full package I generate the DD Specs and the Global Table Spaecs for that environment as well. Once the package has been built Ok and the specs generated I copy the six spec files into the Package name Spec file on the Deployment Server so every time I deploy this full package the specs are sent out with the package as well.

Hope this is of use.

Steve
 
Thanks to all for your responses, but my real question is: When running R92TAM and R98CRTGL, where are these built from? What is the source that is read to build the DD and GLBLTBLs? Is it the Enterprise Server?

B733.2, SP 15, Oracle 8.1.6, HP 9000
Win2K, Citrix 1.8, NFuse
 
I think you are missing a step here....

Either you copy DD specs before the compression or copy the files and then
recopress it. This way the newly generated files DD specs should be inculded
in those cab files.
----- Original Message -----
From: "sharling" <[email protected]>
To: <[email protected]>
Sent: Monday, February 18, 2002 10:29 AM
Subject: Re: DD, GLBL TBL and Package Build


Spaecs for that environment as well. Once the package has been built Ok and
the specs generated I copy the six spec files into the Package name Spec
file on the Deployment Server so every time I deploy this full package the
specs are sent out with the package as well.
http://www.jdelist.com/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=2
9056



Win NT 4.0, SQL 7.0,Xe sp 16.1
 
Steve,

You need to be a little careful here. You can copy your DD and Global
Table files to the appopriate spec directory for particular environments
and packages on the Deployment Server, however, if you are using compressed
packages for deployment, you must recompress whatever package you are going
to deploy or these updated files will not get deployed with your package.

In other words, whenever you put files in package directories you must
recompress the parent if you wish to deploy those new files.

If you are not using compressed packages, you may ignore everything I
mentioned above.

Thanks,


James A. Wilson
Technical - CNC
 
they are built from the F987* series of tables

OneWorld Xe Sp16_018, W2k, W2K TSE, SQL 2K on Compaq Proliant.
 
the source for the DD are the F9200...tables on the Enterprise-Server where your System Database is. The Globaltables are build from your CentralObjects (normally at the Enterprise Server)depending from the pathcode you are logged in at your Client machine.

kind regards

AS/400 V5R1 OW Xe SP18_C1
 
James

Thanks for the reply. Luckily I don't use compression on my package builds which is fortunate because I haven't considered compressing my spec files if I had used compression on the builds.

Thanks for the information though,

Steve Harlington
 
Hello

I am not using compression on my package builds so I don't have to compress
the spec files.

Thanks for the reply though, Its warming to think there are so many CNC
experienced people out there.

Cheers
Steve
 
James

Thanks for the reply. Luckily I don't use compression on my package builds
which is fortunate because I haven't considered compressing my spec files if
I had used compression on the builds.

Thanks for the information though,

Steve Harlington
 
When you deploy a full package to a workstation, take a look at your workstation at c:\b7\environment\spec.
You´ll see that dddict.* and ddtext.* and glbtbl.* files are almost
0 KB.
OneWorld will JIT from enterprise server all the data dictionary fields, as you need them.
So, it´ll bring the most recent version of the field.
The global tables will be JITed as you access the tables, I´m not sure but I think that will come from the central objects.
If you change you DD specification and install a full package, you don´t need to recompress, build update package or anything, because OneWorld will give you the most recent DD.


Robson Candêo
Placas do Paraná - Brazil
Xe, SP16, AS400 with Central Objects on it, Windows 2000.
 
Pianosynth,

To answer your original questions...

1 - Where are dd specs built from?
They are built from the F92* tables in the DD7333 data source on the enterprise server.

2 - Where are the gbltbl spec built from?
They are built from the LOCAL specification files in the pathcode directory on the workstation you are using to build them.

In other words, the process should look something like...

1 - Build full package for pathcode DV7333. Where you build it or on what machine does not matter.
2 - Install this package to workstation A.
3 - On workstation A, run the R92TAM to create the dd specs. As you probably know, these files are created in the b7 directory on the workstation.
4 - Copy the dd specs to the local workstation A directory b7/dv7333/spec.
5 - On workstation A, signed onto the DV7333 pathcode, run the R98CRTGL. This creates gbltbl.ddb and gbltbl.xdb in the b7/dv7333/spec directory.
6 - Copy both the dd spec files and glbltbl spec files to a directory on the deployment server to save, as well as into the spec directory of the fill package on the deployment server.
7 - As the others have mentioned, you will have to recompress the full package to incorporate the new spec files into the package cab files for deployment.

Hope this explains :)

owguru (at least I'm trying :)
>all versions
>all platforms
 
Back
Top