PAC Requirements and Best Practices

PAC requirements

Your PACs must conform to the following requirements:

All enterprise server instances in a PAC must be the same bitism.
All machines participating in the PAC must have the same product version installed.
This will avoid using inconsistent program versions between enterprise server instances.
All machines participating in the PAC must be using the same version of the same operating system.
Note:
- This is enforced when an enterprise server instance in a PAC is cold started, it determines the operating system version for the rest of the PAC members. If any enterprise server instance attempts to warm start and the version does not match it will be rejected.
- This minimizes the chance of a user programs failing to run on some of the enterprise server instances due to differences in OS-related functionality support.
TRANCLASS is not supported in a PAC.
Prior to cold starting a PAC, ensure that you have run the caspac command to initialize the PAC.

Micro Focus recommends you use the following best practice guidelines when using PACs:

Each enterprise server instance requires its own resource definition file (dfhdrdat). Only a subset of resources are stored in the PSOR. An enterprise server instance still require resources that are not available from the PSOR. The same dfhdrdat file should be used in every enterprise server instance in the PAC.
The same SIT and startup list should be used for every enterprise server instance in the PAC.
Use the same program and file paths across a PAC.
Only use the caspac command to modify entries in the SOR. Removing entries manually might lead to unexpected behavior.