HP OpenVMS Systems Documentation

POLYCENTER Software Installation Utility Developer's Guide

Example 3-2 shows the full kit referenced by Example 3-1.

product HP AXPVMS FORRTL V7.1-427 full ;(1)
    if (<software HP AXPVMS VMS version minimum V7.0>) ;(2)
        file [SYSLIB]FOR$DEC$FORRTL.EXE
            source [SYSLIB]FOR$DEC$FORRTL-V70.EXE ;
        file [SYSLIB]FOR$DEC$FORRTL.OBJ
            source [SYSLIB]FOR$DEC$FORRTL-V70.OBJ ;
    else ;
        file [SYSLIB]FOR$DEC$FORRTL.EXE
            source [SYSLIB]FOR$DEC$FORRTL-V61.EXE ;
        file [SYSLIB]FOR$DEC$FORRTL.OBJ
            source [SYSLIB]FOR$DEC$FORRTL-V61.OBJ ;
    end if ;
    if (<software DEC AXPVMS VMS version below V7.1>) ;
        file [SYSLIB]FOR$NXTAFTR.OBJ ;
    end if ;
    file [SYSUPD]FOR$INSTALL_FORRTL.COM ;
    file [SYSTEST]FOR$RTL_IVP.COM ;
    file [SYSTEST]FOR$RTL_IVP.OBJ ;
    file [SYSHLP]FORRTL.RELEASE_NOTES release notes ;
    information RELEASE_NOTES phase after ;
    information POST_INSTALL phase after ;
    execute install "@PCSI$DESTINATION:[SYSUPD]FOR$INSTALL_FORRTL INSTALL"
            remove  "@PCSI$DESTINATION:[SYSUPD]FOR$INSTALL_FORRTL REMOVE";(3)
    execute test "@PCSI$DESTINATION:[SYSTEST]FOR$RTL_IVP" ;
end product ;

1. The PRODUCT statement identifies this as a complete layered product kit for installation of (or upgrade to) FORRTL V7.1-427 on an OpenVMS Alpha system.
2. The IF...ELSE...END IF group conditionally executes statements within the group based on the evaluation of the IF function. In this example, two files named [SYSLIB]FOR$DEC$FORRTL.EXE and [SYSLIB]FOR$DEC$FORRTL.OBJ are always provided. However, the contents of these files vary depending on the version of the OpenVMS product that is installed. Notice the use of the SOURCE option on the FILE statements to select the desired file from the kit to copy to the target disk.
3. The EXECUTE INSTALL...REMOVE statement executes the command procedure PCSI$DESTINATION:[SYSUPD]FOR$INSTALL_FORRTL.COM during installation or upgrade of the product, and also during removal of the product. Instead of providing two command procedures, one is used and a parameter is passed to it to indicate the operation.

The operating system kit provides operating system software, such as OpenVMS. The PDF for an operating system kit must contain a PRODUCT statement with the OPERATING SYSTEM keyword and an END PRODUCT statement as shown in the following example:

product DEC AXPVMS VMS V7.2 operating system ;
   .
   .
   .
end product ;

The operating system kit has the following characteristics:

• It contains all of the material for the product. Therefore, it can be used to install the product for the first time or it can upgrade a previously installed version of the product.
• The product cannot be removed unless the PRODUCT REMOVE command contains the /REMOTE qualifier to remove the operating system on a disk that is not the running system.
• The product can be configured or reconfigured.
• Its PDF can contain OPTION and SOFTWARE statements.
• There can be only one product of type operating system installed on a system disk.
• Except for the kit type designation, the structure of an operating system kit is the same as a full kit; all PDL statements that are allowed in a full kit can be used in an operating system kit.

Example 3-3 shows an operating system kit.

product HP AXPVMS VMS V7.1 operating system ;(1)
    upgrade version minimum V6.1 version below A7.2;(2)
   .
   .
   .
    directory [SYSEXE] ;(3)
    directory [SYSFONT] ;
    directory [SYSFONT.DECW] ;
    directory [SYSFONT.DECW.100DPI] ;
   .
   .
   .
    file [SYSEXE]COPY.EXE generation 40069227 ; (4)
    file [SYSEXE]CREATE.EXE generation 40069227 ;
    file [SYSEXE]CREATEFDL.EXE generation 40069227 ;
    file [SYSEXE]DCL.EXE generation 40069227 ;
   .
   .
   .
    file [SYSMGR]SYLOGIN.TEMPLATE generation 40069227 ;
    file [SYSMGR]SYLOGIN.COM generation 40069227 (5)
        source [SYSMGR]SYLOGIN.TEMPLATE write ;
   .
   .
   .
    option ACCOUNTING ;
        file [SYSEXE]ACC.EXE generation 40069227 ;
    end option ;
    option UTILITIES ; (6)
        option MAIL ;
            file [SYSEXE]MAIL.COM generation 40069227 ;
            file [SYSEXE]MAIL.EXE generation 40069227 ;
            file [SYSEXE]MAIL_OLD.EXE generation 40069227 ;
            file [SYSEXE]MAILEDIT.COM generation 40069227 ;
            file [SYSEXE]MAIL_SERVER.EXE generation 40069227 ;
            file [SYSHLP]MAILHELP.HLB generation 40069227 ;
        end option ;
   .
   .
   .
        option DUMP ;
            file [SYSEXE]DUMP.EXE generation 40069227 ;
        end option ;
        option HELP_LIBRARY ;
            scope global ;
              file [SYSHLP]HELPLIB.HLB generation 40069227 release merge ;(7)
            end scope ;
        end option ;
    end option ;
   .
   .
   .
    option REMOVE_OBSOLETE ;
        remove ; (8)
            file [SYSLIB]LIBOTS.OLB ;
            file [SYSLIB]EDTSHR_TV.EXE ;
        end remove ;
    end option ;
end product ;

1. The PRODUCT statement identifies this as a complete operating system kit for installation of (or upgrade to) OpenVMS V7.1 on an Alpha system.
2. The UPGRADE statement specifies that if this kit is being used to upgrade the VMS product then the previous version must be within the stated range of versions. However, if this is an initial installation of the operating system, the UPGRADE statement is ignored.
3. This DIRECTORY statement creates the directory [SYS0.SYSCOMMON.SYSEXE], that is, SYS$COMMON:[SYSEXE].
4. These FILE statements copy files to the target system disk. The VMS product places generation numbers on all objects that it provides to aid in object conflict detection and resolution when other products (or patch and partial kits to the operating system) that may replace these objects are installed.
5. This FILE statement provides [SYSMGR]SYLOGIN.COM from a template file. The WRITE option indicates that customers are allowed to edit this file. On upgrade, if this file exists it will not be replaced.
6. This OPTION...END OPTION group demonstrates how options can be nested. The MAIL option is presented to the user only if the UTILITIES option is selected.
7. The FILE statement that provides [SYSHLP]HELPLIB.HLB is enclosed in a SCOPE GLOBAL...END SCOPE group to allow other products to freely make updates to this library.
   The RELEASE MERGE keyword phrase indicates that library modules propagate during an upgrade. For example, if a layered product adds a module to HELPLIB.HLB, this module is automatically inserted into the new library file that is provided by the VMS product during an upgrade of the operating system.
8. The REMOVE...END REMOVE group within an OPTION...END OPTION group deletes all objects specified in the remove group if the user selects the option.

The platform kit installs a product suite, which is an integrated set of software products. It may provide files that are common to all products in the suite, or it may not provide any files. It does, however, contain software references to one or more other products. These references can be either required, optional, or a combination of required and optional. For example, the OPENVMS platform kit always installs the OpenVMS operating system product and asks whether to optionally install system integrated products such as HP DECwindows Motif and HP TCP/IP Services for OpenVMS.

The PDF for a platform kit must contain a PRODUCT statement with the keyword PLATFORM and an END PRODUCT statement, as shown in the following example:

product HP AXPVMS OPENVMS V7.2 platform ;
   .
   .
   .
end product ;

The platform kit has the following characteristics:

• It contains all of the material that is common to the product suite. Therefore, it can be used to install the product suite for the first time or it can upgrade a previously installed version of the platform. As stated, product material is optional for a platform kit. It should, however, contain one or more SOFTWARE statements to reference other products.
• Products referenced do not have to be present when the platform kit is packaged because referenced products are not bundled into the platform kit. However, when you copy a platform, products that are referenced by SOFTWARE statements with the COMPONENT option must be present.
• The platform product can be removed, configured, or reconfigured.
• Its PDF can contain OPTION and SOFTWARE statements.
• Except for the kit type designation, the structure of a platform kit is the same as a full kit; all PDL statements that are allowed in a full kit can be used in a platform kit.

Example 3-4 shows a platform kit.

product HP AXPVMS OPENVMS F7.1 platform ; (1)
    upgrade version minimum A7.1 version below V7.2; (2)
    software HP AXPVMS VMS version required F7.1 ; (3)
    option DWMOTIF_KIT ; (4)
        software HP AXPVMS DWMOTIF version minimum V1.2-4 ;
    end option ;
    option DECNET_OSI_KIT ;
        software HP AXPVMS DECNET_OSI version minimum K7.1 ;
    end option ;
    option UCX_KIT ;
        software HP AXPVMS UCX version minimum V4.1-12 ;
    end option ;
end product ;