Appendix B, Moving HELP text
This appendix shows you how to move VDM HELP screens between your system help library and private, user help library. You would do this if you had previously installed VDM help into the system help library and did not want public access to the help screens.
Moving HELP from system to a user library
To move the VDM HELP screens from the system HELP library to a private, user help library:
1. Delete help text from the system help library:
 |
$ LIBRARY/DELETE=VDM SYS$HELP:HELPLIB.HLB |
2. Define a user help library logical.
|
2.1 Enter the command "$ SHOW LOGICAL HLP$*" to find a user library logical name that has not previously been assigned (logical names may be HLP$LIBRARY, HLP$LIBRARY_1, HLP$LIBRARY_2, ... ,HLP$LIBRARY_n) |
2.2 Assign the help logical as follows:
|
$ DEFINE/SYSTEM HLP$LIBRARY_n VDM_DOC:VDM.HLB |
|
If you define the logical in the SYSTEM table, everyone will be able to access the HELP. If you define it in your PROCESS table, only you will be able to access the HELP. If you use the SYSTEM table, you should add a line to the VDM system startup to define it every time the system is booted. If you use the PROCESS table, you should add a line to your LOGIN.COM. |
Moving HELP from a user to the system library
To move the VDM HELP screens from a private, user help library to the system help library:
1. Find the logical pointing to the user help library for VDM and deassign it.
|
$ SHOW LOGICAL HLP$LIBRARY* |
|
$ DEASSIGN HLP$LIBRARY_n |
2. Add the VDM help library to the system help library.
|
$ LIBRARY/REPLACE/HELP SYS$HELP:HELPLIB.HLB - |
|
_$ dev:[VDM.DOC]VDM.HLP |
3. If the HLP$LIBRARY_n logical was not the last logical in the sequence of user help library logicals, you must assign something else to it. HELP stops translating HLP$LIBRARY_n logicals when it encounters the first one which isn't defined.
Appendix C, Moving command definitions
This appendix shows you how to install the VDM command definition in your system DCLTABLES, remove it from the DCLTABLES or access it from the VDM directory. You would remove the VDM command definition if you had previously installed the VDM command definition in the system command definition library and did not want public access to the command definition.
To install the command definition in the system table:
1. Check which version of the table is installed
$ INSTALL
INSTALL> LIST SYS$LIBRARY:DCLTABLES.EXE
INSTALL> EXIT
2. Replace the VDM command definitions in the table:
$ SET COMMAND/TABLE=SYS$LIBRARY:DCLTABLES.EXE -
_$ /OUTPUT=SYS$LIBRARY:DCLTABLES.EXE -
_$ /REPLACE VDM_CDU:VDM
NOTE: Ensure the new DCLTABLES.EXE are in the same directory as the previous tables.
3. Install the new table:
$ INSTALL
INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE
INSTALL> EXIT
4. Log out and back in to get a copy of the new table.
To remove the command definition from the system table, type:
|
$ SET COMMAND/DELETE=VDM/TABLE=SYS$LIBRARY:- |
_$ DCLTABLES.EXE/OUTPUT=SYS$LIBRARY:DCLTABLES.EXE
To access the command definition from the VDM directory, type:
$ @VDM_COM:INSTALL_CDU.COM
Appendix D, Removing VDM from your system
This appendix shows you how to remove VDM from your system if you received a demo, decided to return it and want to remove VDM from your system.
NOTE: There is a command procedure REMOVE_VDM.COM which you can adapt to perform many of these steps rather than keying the commands individually.
Delete directories
To remove the VDM directories from your system, type:
|
$ DELETE SYS$SYSDEVICE:[VDM...]*.*;*/EXCLUDE=(*.DIR) |
This removes all non_directory files from the directory structure.
To delete the VDM directory file from your system, set the protection to allow delete and delete the directory files. Type:
$ SET FILE/PROTECTION=S:RWED SYS$SYSDEVICE:[VDM...]*.DIR
|
$ DELETE SYS$SYSDEVICE:[VDM...]*.*;* |
$ DELETE SYS$SYSDEVICE:[000000]VDM.DIR;*
Remove HELP screens
If help screens were added into the system help library, remove them by typing:
|
$ LIBRARY/DELETE=VDM SYS$HELP:HELPLIB.HLB |
If help screens were added into a private, user help library, follow the procedure outlined in Appendix B to remove them.
Remove command definition
If the VDM command verb was added to the DCLTABLES, remove it by typing:
|
$ SET COMMAND/DELETE=VDM/TABLE=SYS$LIBRARY:- |
_$ DCLTABLES.EXE/OUTPUT=SYS$LIBRARY:DCLTABLES.EXE
Note: Remember to remove the command:
@VDM_COM:INSTALL_CDU.COM
from your LOGIN.COM and any other command procedures.
Deassign system logical names
Deassign the system logicals required by VDM:
|
$ DEASSIGN/SYSTEM VDM_CDU |
|
$ DEASSIGN/SYSTEM VDM_COM |
|
$ DEASSIGN/SYSTEM VDM_DAT |
|
$ DEASSIGN/SYSTEM VDM_DOC |
|
$ DEASSIGN/SYSTEM VDM_EXE |
Remove SYS$MANAGER files
Delete the files VDM_STARTUP.COM and VDM_SYSTEM_LOGICALS.COM created by the installation procedure from the SYS$MANAGER directory and remove the line that executes this procedure from SYS$MANAGER:SYSTARTUP_V5.COM or SYS$MANAGER:SYSTARTUP_VMS.COM (OpenVMS 6.0).
Appendix E, Software licenses
This appendix describes the terms of the VDM software license. Customers may license VDM separately or as part of the Cohort Version 2 suite of system management utilities.
VDM and Cohort are sold under the following types of licenses:
CPU License
A CPU license allows you to run on one CPU at a time. It does not matter what the AXP or VAX model is.
Site License
A Site License allows you to run on any number of AXP or VAX systems owned by your company within one city. For a nominal amount a site license can be upgraded to include any number of VAX and AXP systems within one city.
Corporate License
A Corporate License allows you to run VDM on any number of AXP or VAX systems owned by your company within one country. For a nominal amount a corporate license can be upgraded to include any number of VAX and AXP systems within one country.
Global License
A Global License allows you to run VDM on any number of AXP or VAX systems worldwide. For a nominal amount a global license can be upgraded to include any number of VAX and AXP systems worldwide.
License Validation
You do not have to sign the license and return it. It comes into effect when you make use of the product.
DIGITAL
None of Saiga Systems products require any Digital licenses beyond that for OpenVMS. If you plan to make changes to the products, you must have a FORTRAN license or access to a system that has such a license.
Upgrading your license
You can upgrade from one license to another by paying the difference between the two.
Appendix F, File Flags
This appendix lists the keywords you can use with the /FLAGS qualifier.
BADACL File contains a bad ACL. ACL is not used for protection checking.
BADBLOCK File contains a bad block.
CONTIGB File is best-try contiguous.
CONTIG File is contiguous.
|
DIRECTORY File is a directory. |
ERASE File will be erased (overwritten) on delete.
LOCKED File is locked.
MARKDEL File is marked for deletion.
NOBACKUP File will not be backed up.
NOCHARGE File is not charged to owner.
NOMOVE File cannot be moved.
READCHECK File requires read check operations. All read operations are verified.
SPOOL File is a temporary spool file.
WRITCHECK File requires write check operations. All write operations are verified.
WRITEBACK Write-back cache may be used.