Suggested Package Names
You should maintain two versions of each package, an A and a B version, so that you can alternate between these versions when you build packages. The advantage of this approach is that users always have a package available to them, even when you are building the latest version of that package. For example, package PRODB would be available to users while you are building PRODA. Then, after you release PRODA, you would build the next package into PRODB, and so on. This setup gives you two full packages (A and B) for production, as illustrated in this table:
Package Name |
Description |
|---|---|
PD920FA |
Standard Production Full A |
PD920FB |
Standard Production Full B |
Update packages might be named with the path code followed by "UA" or "UB" as shown:
Update Package Name |
Description |
|---|---|
PD920UA |
Production Update Package 1 |
PD920UB |
Production Update Package 2 |
PD920UA |
Production Update Package 3 |
PD920UB |
Production Update Package 4 |
A deployed server package cannot be revised, rebuilt, or deleted. It must be replaced with another package first. For this reason, you must have at least two server packages available so that you can alternate between them.
The maximum length for a package name is nine characters unless the enterprise sever is IBM i.
(Tools Release 9.2.7.3) If the enterprise server is IBM i, the addendum which is added to the package name library is taken into consideration and the maximum limit is 10 characters. For IBM i, if your package is DV920FA and the addendum is US, the package library will be DV920FAUS which is 9 characters and is valid. Any package with a package name and addendum greater than 10 characters will fail.