[an error occurred while processing this directive]

HP OpenVMS Systems Documentation

HP OpenVMS Version 8.2 New Features and Documentation Overview

Chapter 5
5	Associated Products Features
5.1	ATI RADEON 7500 Graphics
5.2	Common Data Security Architecture (CDSA) Now Supports a New Encryption Type
5.3	Kerberos for OpenVMS
5.4	HP SSL for OpenVMS
5.5	HP TCP/IP Services for OpenVMS Version 5.5
Chapter 6
6	Host-Based Minimerge (HBMM) in Volume Shadowing for OpenVMS
6.1	HBMM Configuration Requirements
6.2	HBMM Restrictions
6.2.1	Cluster Configuration Restrictions
6.2.2	Shadow Set Member Restrictions
6.2.3	System Parameter Restrictions
6.3	HBMM in a Mixed-Version or Mixed-Architecture OpenVMS Cluster System
6.4	Overview of Full Merge and Minimerge Operations
6.4.1	Merge Resulting from a System Failure
6.4.2	Merge Resulting from Mount Verification Timeout
6.4.3	Merge Resulting from Use of SET SHADOW/DEMAND_MERGE
6.4.4	Comparison of Merge and Minimerge Operations
6.5	Overview of HBMM
6.5.1	Bitmaps: Master and Local
6.5.2	HBMM Policies
6.6	HBMM Policy Specification Syntax
6.7	Rules Governing HBMM Policies
6.8	Guidelines for Establishing HBMM Policies
6.8.1	Selecting the Systems to Host Master Bitmaps
6.8.2	Setting the Bitmap RESET_THRESHOLD Value
6.8.3	Using Multiple Policies
6.9	Configuring and Managing HBMM
6.9.1	How to Define an HBMM Policy
6.9.2	How to Assign an HBMM Policy to a Shadow Set
6.9.3	How to Activate HBMM on a Shadow Set
6.9.4	How to Disable HBMM on a Shadow Set
6.9.5	How to Remove a Policy Association from a Shadow Set
6.9.6	How to Change a Policy Assignment of a Shadow Set
6.9.7	How to Delete a Named Policy from the Cluster
6.9.8	How to Apply a Changed DEFAULT Policy
6.9.9	How to Display Policies
6.9.10	How to Display the Merge Status of Shadow Sets
6.9.11	How to Prevent Merge Operations on a System
6.9.12	Considerations for Multiple-Site OpenVMS Cluster Systems
6.10	New System Parameters That Affect HBMM
6.10.1	SHADOW_REC_DLY Parameter
6.10.2	SHADOW_HBMM_RTC Parameter
6.11	Use of /DEMAND_MERGE When HBMM Is Enabled
6.12	Prioritizing Merge and Copy Operations
6.12.1	Default Management of Merge and Copy Operations
6.12.2	Hierarchy of Transient State Operations
6.12.3	Assigning Priorities
6.12.4	Displaying Priority Values
6.12.5	Controlling Which Systems Manage Merge and Copy Operations
6.12.6	Managing Merge Operations
6.12.7	Managing Copy Operations
6.12.8	Managing Transient States in Progress
6.13	Visible Impact of Transient State Events
Chapter 7
7	Linker Utility
7.1	Linker Utility New Features
7.1.1	Differences When Linking on OpenVMS I64 Systems
7.1.1.1	Data Types of Symbols must Match on I64
7.1.1.2	Specifying Based Clusters Vary by OpenVMS Platform
7.1.1.3	Handling of Initialized Overlaid Program Sections on OpenVMS I64 Systems
7.1.1.4	Behavior Difference When Linking ELF Common Symbols
7.1.1.5	Flags Set When /TRACEBACK, /DEBUG, and /DSF are Used
7.1.2	New Aspects for Linking on OpenVMS I64 Systems
7.1.2.1	Understanding Linkage Messages
7.1.2.2	Considerations for Images Compiled with Reduced Floating Point Model
7.1.2.3	Considerations for Linking with ELF Groups and UNIX-style Weak Symbols
7.1.3	New Linker Qualifiers for OpenVMS I64
7.1.3.1	New /BASE_ADDRESS Qualifier
7.1.3.2	New /SEGMENT_ATTRIBUTE Qualifier
7.1.3.3	New /FP_MODE Qualifier
7.1.3.4	New Linker Qualifiers: /EXPORT_SYMBOL_VECTOR and /PUBLISH_GLOBAL_SYMBOLS
7.1.3.5	New GROUP_SECTIONS and SECTION_DETAILS keywords for the /FULL Qualifier
7.1.4	New Linker Options for OpenVMS I64
7.1.4.1	New Alignments for the PSECT_ATTRIBUTE Option
7.1.5	New Ways to Use Existing Linker Qualifiers and Options
7.1.5.1	Mixed-Case Arguments in Linker Options on I64 Systems
7.1.5.2	Conventions for Specifying Image Names
7.1.5.3	Using the PSECT_ATTRIBUTE Option to Specify Alignment
7.1.5.4	Special Linker Handling of Nonexistent Files
7.1.6	New OpenVMS I64 Linker Map
Part 2
Part 2	OpenVMS Documentation

Contents

Index