You can recompress the full package -- there's a document on the KG
explaining how
to do this in detail, but the basic idea is that at a time when no one will
be installing
the full package, you run P9622, Package Build History, on the Deployment
Server in
the DEP7333 environment. Search for the full package, and then in the left
pane
of the window, unfold under the package name, where you'll find the date of
the build.
Unfold that to find CLIENT and the names of any servers you built the
package for.
Unfold CLIENT and highlight Compression Options, then click on the Reset
Status
row exit. Set both Spec Build Status and Pack Build Status to 01 and click
Reset.
Check that all the items under Compression Options (BIN32, INCLUDE, etc) now
say "Not Built"
(you'll have to re-find on the screen). Then, highlight the date the
package was built
(NOT the name of the package) and click the Resubmit Build row exit. You'll
be asked
if you want to generate NER -- click Cancel. Then just click OK on the
Report Destination
screen, of course, and the UBEs will run again, only processing the parts
that are
marked as Not Built, which in this case is just the compression. What this
does is recreate
the CAB files in the package directory, which are what is used for the
installation.
The actual directories (lib32, spec, etc) under the package directory are
updated
when you create an update package, but the compressed CAB files are not
rebuilt.
By doing this recompression process, you rebuild those files so that new
installations
of the full package include all the changes from the update packages.
--Scotti Whitmire
DeRoyal Industries
Xe, U6, SP22_E1, AIX 4.3.3, Oracle 8.1.7