| Preface |
|
Preface
|
Preface
|
| Chapter 1 |
|
1
|
Overview
|
|
1.1
|
Features for Software Providers
|
|
1.2
|
Coexistence with VMSINSTAL
|
|
1.3
|
Creating an Installable Kit
|
|
1.3.1
|
Step 1: Make A Plan
|
|
1.3.2
|
Step 2: Gather the Product Material
|
|
1.3.3
|
Step 3: Create a Product Description File
|
|
1.3.4
|
Step 4: Create a Product Text File (Optional)
|
|
1.3.5
|
Step 5: Package the Software Components
|
|
1.3.6
|
Step 6: Test and Debug the Installable Kit
|
| Chapter 2 |
|
2
|
Basic Concepts
|
|
2.1
|
The Product Database
|
|
2.1.1
|
Querying the Product Database
|
|
2.2
|
Software Product Kit Formats
|
|
2.3
|
Software Product Kit Naming Conventions
|
|
2.3.1
|
Sequential Format
|
|
2.3.2
|
Compressed Format
|
|
2.3.3
|
Reference Format
|
|
2.3.4
|
Kit Naming Rules and Conventions
|
|
2.3.5
|
More About the Version Field
|
|
2.3.6
|
Version Information Visible to the OpenVMS Users
|
|
2.3.7
|
More About the Kit Type
|
|
2.3.8
|
Looking at Software Product Name Examples
|
|
2.3.9
|
Input and Output Versions of the PDF and PTF
|
|
2.4
|
User-Defined Logical Names
|
|
2.5
|
Utility-Defined Logical Names
|
|
2.5.1
|
PCSI$SOURCE, PCSI$DESTINATION, and PCSI$SCRATCH
|
|
2.5.2
|
PCSI$$RECOVERY_MODE and PCSI$$SAVE_RECOVERY_DATA
|
|
2.5.3
|
PCSI$$COMMAND_LINE
|
|
2.5.4
|
PCSI$$CONFIRM
|
|
2.6
|
Managed Objects
|
|
2.6.1
|
Creating Managed Objects
|
|
2.6.2
|
Managed Object Conflict
|
|
2.6.3
|
Preventing Managed Object Conflict
|
|
2.6.4
|
Managed Object Replacement and Merging
|
|
2.6.5
|
Managed Object Scope and Lifetime
|
|
2.7
|
Creating an Integrated Platform (Product Suite)
|
