Updated: 11 December 1998 |
POLYCENTER Software Installation Utility Developer's
Guide
Previous | Contents | Index |
The POLYCENTER Software Installation utility supports seven kit types that can be grouped into three broad categories:
You use the PRODUCT PACKAGE command to package (or build) a product kit. The output of the packaging process is an installable kit (in either sequential copy format or reference copy format) that contains:
The full product name (that is, the string producer-base-product) must be unique among all products installed on a system. This implies, for example, that there could be two FORTRAN compilers installed from different companies (such as DEC-AXPVMS-FORTRAN and XYZCORP-AXPVMS-FORTRAN), but there cannot be two patch kits with the same full name that are intended to apply to different products (such as ABC-VAXVMS-ECO1 for ABC-VAXVMS-COBOL and ABC-VAXVMS-ECO1 for ABC-VAXVMS-C).
The following sections describe each type of kit and provide examples
of their product description files.
3.5.1 The Full Kit Type
A full kit provides layered product application software and is the most common type of kit. The PDF for a full kit must contain a product statement with the keyword full and an end product statement, as shown in the following example:
product DEC AXPVMS TEST_A V2.0 full ; . . . end product ; |
The full kit has the following characteristics:
Example 3-1 shows a full kit that references another product.
Example 3-1 PDF for a Full Kit that References Another Full Kit |
---|
product DEC AXPVMS FORTRAN V7.1-1 full ; (1) if (not <software DEC AXPVMS VMS version minimum V7.1>) ;(2) software DEC AXPVMS FORRTL version minimum V7.1 ; end if ; information STARTUP_TASK phase after ; information RELEASE_NOTES phase after ;(3) file [SYSHLP]FORTRAN.RELEASE_NOTES release notes ;(4) file [SYSHLP]FORTRAN_RELEASE_NOTES.PS ; file [SYSHLP]FORTRAN_RELEASE_NOTES.DECW$BOOK ; if (<software DEC AXPVMS FORTRAN90>) ;(5) error REMFORT90 ; end if ; option FORTRAN_90 ;(6) file [SYSEXE]F90$MAIN.EXE generation 2 ; file [SYSMSG]F90$MSG.EXE generation 2 ; module [000000]F90CLD.CLD type command generation 2 module F90 ; module [000000]F90HELP.HLP type help generation 2 module F90 ;(7) end option ; option FORTRAN_77 ; file [SYSEXE]FORT$MAIN.EXE generation 1 ; file [SYSEXE]FORT$FSPLIT.EXE generation 1 ; file [SYSMSG]FORT$MSG.EXE generation 1 ; file [SYSMSG]FORT$MSG2.EXE generation 1 ; module [000000]DEC_FORTCLD.CLD type command generation 1 module FORTRAN ; module [000000]DEC_FORHELP.HLP type help generation 1 module FORTRAN ; end option ; file [SYSLIB]FORSYSDEF.TLB generation 5 ; file [SYS$STARTUP]FORT$STARTUP.COM generation 1 protection private ;(8) file [SYSTEST]FORT$IVP.COM generation 1 protection private ; execute test "@PCSI$DESTINATION:[SYSTEST]FORT$IVP.COM" ;(9) end product ; |
1 RELEASE_NOTES =prompt Type HELP FORTRAN Release_notes for release notes location |
1 REMFORT90 =prompt PRODUCT REMOVE FORTRAN90 before installing Digital Fortran The obsolete DEC Fortran 90 product must be removed before Digital Fortran is installed. To do this, use the command: PRODUCT REMOVE FORTRAN90 |
1 FORTRAN_90 =prompt Digital Fortran 90 compiler This option selects the Digital Fortran 90 compiler. |
Example 3-2 shows the full kit referenced by Example 3-1.
Example 3-2 PDF for a Full Kit |
---|
product DEC AXPVMS FORRTL V7.1-427 full ;(1) if (<software DEC 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 ; |
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 keyword operating system 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:
Example 3-3 shows an operating system kit.
Example 3-3 PDF for an Operating System Kit |
---|
product DEC AXPVMS VMS V7.1 operating system ;(1) upgrade version 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 ; |
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 VMS product and asks whether to optionally install system integrated products such as DECwindows Motif and 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 DEC AXPVMS OPENVMS V7.2 platform ; . . . end product ; |
The platform kit has the following characteristics:
Example 3-4 shows a platform kit.
Example 3-4 PDF for a Platform Kit |
---|
product DEC AXPVMS OPENVMS F7.1 platform ; (1) upgrade version version minimum A7.1 version below V7.2; (2) software DEC AXPVMS VMS version required F7.1 ; (3) option DWMOTIF_KIT ; (4) software DEC AXPVMS DWMOTIF version minimum V1.2-4 ; end option ; option DECNET_OSI_KIT ; software DEC AXPVMS DECNET_OSI version minimum K7.1 ; end option ; option UCX_KIT ; software DEC AXPVMS UCX version minimum V4.1-12 ; end option ; end product ; |
1 DWMOTIF_KIT =prompt DECwindows Motif for OpenVMS Alpha This option installs DECwindows Motif for OpenVMS Alpha, which provides the X Window system graphical user interface. |
You use a partial kit to upgrade a currently installed product, including replacing some of the product's files, providing new files, or removing files. The PDF for a partial kit must contain a product statement with the keyword partial, an upgrade statement, and an end product statement as shown in the following example:
product DEC VAXVMS TEST_A V2.1 partial ; upgrade version required V2.0 ; . . . end product ; |
A partial kit has the following characteristics:
Generally, a new version of a product is provided as a full kit instead of a partial kit because a full kit can be used for either an initial installation or for an upgrade of the product. A partial kit is limited to an upgrade path.
A partial kit, however, is usually much smaller in disk block size than its corresponding full kit. For a very large product, this reduction in size may significantly reduce the time it takes to distribute the kit over the network.
Example 3-5 shows a partial kit.
Example 3-5 PDF for a Partial Kit |
---|
product DEC AXPVMS FORTRAN V7.2 partial ; (1) upgrade version required V7.1-1 ; (2) information RELEASE_NOTES phase after ; information STARTUP_TASK phase after ; file [SYSHLP]FORTRAN.RELEASE_NOTES release notes ; file [SYSHLP]FORTRAN_RELEASE_NOTES.PS ; file [SYSHLP]FORTRAN_RELEASE_NOTES.DECW$BOOK ; file [SYSEXE]FORT$MAIN.EXE generation 4 ; (3) file [SYSMSG]FORT$MSG.EXE generation 4 ; file [SYSMSG]FORT$MSG2.EXE generation 4 ; module [000000]DEC_FORTCLD.CLD type command generation 4 module FORTRAN ;(4) execute test "@PCSI$DESTINATION:[SYSTEST]FORT$IVP" ; end product ; |
Previous | Next | Contents | Index |
Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal |
5952PRO_003.HTML
|