October 2009: Version 7.1 Final has been released; please see 7.1 Release Updates.
This page relates only to the two 7.1 pre-Releases; if you're still running a pre-Release, you should obtain the 7.1 Final Release for the improved documentation and other software improvements.
HP APB customers: For support on the pre-release versions, please contact us directly rather than your HP Customer Support Center, or (if you prefer) be sure to explain to HP Customer Support that you're running a pre-release version and ask them to escalate your case to us for Level 2 support.
Be sure to read the Release Notes (on the CD or downloaded distribution), and contact us if you have any questions.
Do I have pre-release 1 or pre-release 2?
The following VPROC information can be used to determine whether the 7.1 release you have is 7.1 pre-release 1 or 7.1 pre-release 2. Contact us if you need assistance or have a combination of VPROCs that differs from these.
7.1 pre-release 1 7.1 pre-release 2 and 7.1 final* BAL : T0000V07_1_BAL_2510_BQcaFS4 T0000V07_1_BAL_2573_CAoWESw BALCPU : T0000V07_1_BALCPU_2504_BQcaFS8 T0000V07_1_BALCPU_2504_CAkTAQE BALDLL : T0000V07_1_BALLIB_2494_BQcaFS8 T0000V07_1_BALLIB_2494_CAkTAQE BALLIB : T0000V07_1_BALLIB_2494_BQcaFS8 T0000V07_1_BALLIB_2494_CAkTAQE BALMON : T0000V07_1_BALMON_2504_BQcaFS8 T0000V07_1_BALMON_2504_CAkTAQE BALUPD : T0000V07_1_BALUPD_2504_BQcaFS8 T0000V07_1_BALUPD_2504_CAkTAQE APB : T0302V07_1_APB_2510_BQcaFS8 T0302V07_1_APB_2573_CAoWESw APBCPU : T0302V07_1_APBCPU_2504_BQcaFS8 T0302V07_1_APBCPU_2504_CAkTAQE APBDLL : T0302V07_1_APBLIB_2494_BQcaFS8 T0302V07_1_APBLIB_2494_CAkTAQE APBLIB : T0302V07_1_APBLIB_2494_BQcaFS8 T0302V07_1_APBLIB_2494_CAkTAQE APBMON : T0302V07_1_APBMON_2504_BQcaFS8 T0302V07_1_APBMON_2504_CAkTAQE APBUPD : T0302V07_1_APBUPD_2504_BQcaFS8 T0302V07_1_APBUPD_2504_CAkTAQE
* The only difference between 7.1 pre-release 2 and 7.1 final is improved documentation.
Upgrading from 7.1 pre-release 1 to 7.1 pre-release 2
You can upgrade from pre-release 1 to pre-release 2 by replacing only the BAL or APB program with the new one. (The other object files, even though their VPROCs are slightly different, are functionally unchanged.) The documentation has been improved, as well, so you may want to obtain the 7.1 pre-release 2 documentation as well.
Known Problems and Workarounds in Both pre-release 2 and pre-release 1
- The documentation has not yet been completely updated for using the Balancer/APB library with TNS/E Native creators. Only the "Linking the Balancer/APB to Other Programs" subsection (in the "Balancer/APB Library" chapter) is complete in this regard; elsewhere in the manual it often still only refers to using BIND for non-Native process creators. If you need help in using BALDLL/APBDLL on TNS/E systems, please contact us. Upgrade to 7.1 Final to get complete documentation.
- The Overseer software (the Windows-based performance monitor and its NonStop server components) are not included in either Balancer pre-release. If you have version 5.1, 6.1, or 6.2 of the Overseer, it will continue to work, unmodified, on TNS/R and TNS/E systems. New TNS/R and TNS/E Native versions of the NonStop Overseer server software are included in the final 7.1 release.
- The PDF version of the documentation is not included in either pre-release.
Known Problems and Workarounds in pre-release 1
- It is possible for some fully-qualified program name rules in
eAPBPROGto be silently ignored, even though they are perfectly valid.
The workaround is to use partially-qualified program name rules (e.g.
$SYSTEM.SYSTEM.PATHMON). Upgrade to 7.1 pre-release 2 or 7.1 Final to eliminate this problem.
- The new logic for handling PROGID'd programs relative to the eBALUSER/eAPBUSER configuration file, as described in the 7.1 Release Notes, works as documented for PROGID'd creator processes, but still uses the creating user's rules for PROGID'd object files (i.e. created processes). Upgrade to pre-release 2 or 7.1 Final to eliminate this problem.
- Short cpu masks (like "11101" and "11100") are misinterpreted when the last digit is a "1" -- the "1" is not automatically extended through the rest of the mask as it should be. The workaround is to specify a full 16-bit mask. Upgrade to pre-release 2 or 7.1 Final to eliminate this problem.