Adding file dependency information, Specifying a, Destination subvolume or file name – HP Integrity NonStop H-Series User Manual
Page 384
![background image](/manuals/397210/384/background.png)
Running CNFGINFO
DSM/SCM User’s Guide — 529846-014
C - 11
Specifying File Information
Specifying a Destination Subvolume or File Name
Enter or modify the information in the Subvolume and New filename fields as needed.
The TSV where the file will be placed depends on the file’s function. The destination
subvolume you specify for a file depends on the file’s function:
Requiring That a File Must Be Licensed for Use by the Target System
Check the License file check box. This check box is available only if you are logged
on as the super ID (255,255).
Adding File Dependency Information
ADDIF and DELIF lists are typically used when a DSV might contain an optional
product, such as SQL/MP or Safeguard. The problem is that existing products on your
system might contain calls to the optional product.
The A0CINFO file can optionally include an ADDIF list or a DELIF list for each product
file:
The ADDIF list is a list of products that, if they are in a software revision, cause the
file to be included in the revision. If any listed products are in the revision, the file is
included. If none of the products are in the revision, the file is not included.
The DELIF list is a list of products that, if they are in a software revision, cause the
current file to be excluded from the revision. The file is included only if none of the
listed products is in the revision.
DSM/SCM uses these lists to:
Determine which product files to copy to the new revision when creating a new
software revision
Determine what files to input to system generation when building the activation
package
You must allow for the case where the optional product is not present:
Function
Destination
DOCPRINT
SOFTDOC, if the file is a softdoc
ZRLSEDOC or RLSEDOC, if the file is a release document
INSTALL
PDTSYS
MIGRATION
PDTSYS
PRIV DECS
TSV name
SYSGEN
Depends on the file’s use in the system generation process; for example,
SYSnn or CSSnn.
TACL
SYSnn subvolume
USER
TSV name