Retaining old packages

How long should old packages be retained on the deployment server and the enterprise server? Can "old" packages (full & update) be deleted after a new full package has been created? I just created new full packages for DV & PY. The old packages are taking up a lot of space on our enterprise (AS400) server.

Thanks,

Tgore :

It depends on how useful would these packages be to you.
I usually keep two packages : the newest and the previous one.

Sebastian Sajaroff (JDELIST)

----------------------------------------------------------------------------
Strictly Personal and Confidential.
This email may contain confidential and proprietary material for the sole
use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient please contact
the sender and delete all copies.Thanks.
.
Este mensaje es confidencial.
Puede contener informacion amparada por el secreto profesional. Si usted ha
recibido este e-mail por error, por favor comuniquenoslo inmediatamente via
e-mail y tenga la amabilidad de eliminarlo de su sistema; no debera copiar
el mensaje ni divulgar su contenido a ninguna persona. Muchas gracias.
----------------------------------------------------------------------------

Tgore,

enterprise server?
We keep the following: Production(PD)= current + 2; CRP (PY)=Current + 1;
Development (DV)=Current.

has been created?
Yes, the old full and updates can be deleted. I recommend that you delete
the updates then the full, to ensure that you aren't left with hanging
updates.

Tom Davidson
Xe, SP 19.1 Update 2 + 700+ ESU's; ES: AS/400 (2); CO on SQL 7.0; DS:
Win2K; TSE 2000/Metaframe XP FR1





OW 7333 SP 19.1, WIN2K, TSE 2000, Metrframe XP FR 1, CO SQL 7.0

T,
in my opinion it should not be necessary to keep more then two
generations of packages, that is a new current one and a previous. I
would delete all other old full and update packages. I would as well re-
compress my previous full package and delete all updates to that previous
package. The b7333\PATHCODE\package directory gets too easily cluttered
up.
To save further disk space you may always delete the contents of the pack
directory on the DS for server packages. Once the server package is
build, the .pak files are of no use any more.

On the ES it should be necessary to keep only the previous full package,
delete all old updates.

My two centavos, Gerd

Thanks to all. Lots of useful information. As a side note-I *always* recompress after an update package has been built.

We don't keep too long. If it installs correctly and works fine we'll delete them asap so that we keep enough space free on the AS400.

Another reason why we do this is that the previous Full Package has been corrupted.

Has anyone ever reverted back to a previous parent package after deploying a new one?