From: Didier Morandi [DMo@ims.ch]
Sent: Friday, April 27, 2001 2:55 AM
To: Info-VAX@Mvb.Saic.Com
Subject: [INFO] PCSI for Newbie version x0.0-0.00



                        ===================
                        POLYCENTER_INFO.TXT
                        ===================


                   V1.1-0 27-apr-2001 D. Morandi
            (for any questions: Didier.Morandi@wcxn.org)
             or http://groups.yahoo.com/group/vmsinstal


The PolyCenter Software Installation utility (aka PCSI) supersedes the
VMSINSTAL.COM DCL command procedure.

To build a kit with PCSI, the following actions should be performed:

1. Documentation
================

Read the OpenVMS System Management Utilities Reference Manual M-Z pages 3-1 
to 3-55 and the Polycenter Software Installation Utility Developer's Guide.


2. Check-list
=============

Fill the questionaire pp. 3-1 to 3-4 of the above Developer's Guide.


3. Product Description File (PDF)
=================================

Write the .PCSI$DESC file such like this:
(the comment character is "--")

--[start of TOTO.PCSI$DESC]-----------------------------------------------
--
product IMS VMS TOTO v1.0-0 full;
--
if (<software DEC AXPVMS version below V7.2-1>);
    error UNSUPP_VMS_VER abort;
endif;
--
execute preconfigure "@PCSI$SOURCE:[TEMP]TOTO$PRE_CONFIGURE.COM" interactive
        uses [TEMP]TOTO$PRE_CONFIGURE.COM;
--
rights identifier TOTO with "/attributes=resource";
--
directory [TOTO] owner TOTO protection private
access control
        ("(IDENTIFIER=[TOTO],ACCESS=READ+EXECUTE)",
         "(IDENTIFIER=[*,*],         ACCESS=NONE)",
         "(IDENTIFIER=[TOTO],OPTIONS=DEFAULT,ACCESS=READ+EXECUTE)");
--
account TOTO with (
 "/uic=[200,010]/account=TOTO/device=MYDISK:/directory=[TOTO]",
 "TOTO_id",
 "/pwdlifetime=""300-""");
--
file [SYSMGR]TOTO.COM owner TOTO protection private
access control
        ("(IDENTIFIER=[TOTO],ACCESS=READ+EXECUTE)",
         "(IDENTIFIER=[*,*], ACCESS=NONE)");
--
file [SYSEXE]TOTO.EXE owner TOTO protection private
access control
        ("(IDENTIFIER=[TOTO],ACCESS=EXECUTE)",
         "(IDENTIFIER=[*,*], ACCESS=NONE)");
--
file [SYSHLP]TOTO.HLP owner TOTO protection private
access control
        ("(IDENTIFIER=[TOTO],ACCESS=READ)",
         "(IDENTIFIER=[*,*], ACCESS=NONE)");
--
execute postinstall "@PCSI$SOURCE:[TEMP]TOTO$POST_INSTALL.COM" interactive
        uses [TEMP]TOTO$POST_INSTALL.COM;
--
end product;
--
--[end of TOTO.PCSI$DESC]-----------------------------------------------

 
4. Product Text File (PTF)
==========================

Create the help and errors text file like this:

--[start of TOTO.PCSI$TEXT]-----------------------------------------------

=product IMS VMS TOTO v1.0-0 full;
1 UNSUPP_VMS_VER
=prompt OpenVMS 7.2-1 required.
The version of TOTO you are installing runs only under OpenVMS 7.2-1
or higher.

Please check whether you are installing this software on the right
system, or do upgrade this system to OpenVMS 7.2-1 or higher.

--[end of TOTO.PCSI$TEXT]-----------------------------------------------


5. Pre and Post installation
============================

Write the DCL pre and post-installation procedures which should (eventually) be
executed before and after the installation. A standard name for the
pre-configuration procedure could be TOTO$PRE_CONFIGURE.COM and for the
post-installation TOTO$POST_INSTALL.COM 


6. Packaging
============

Build a DCL procedure to create the .PCSI kit.
Example:

$ product package TOTO - 
     /base=VMS - 
     /producer=IMS -                     ! the name of your company
     /source=MYDISK:[TOTO.PDF] -         ! where to find PDF and PTF 
     /destination=MYDISK:[KITS] -        ! where to put .PCSI file 
     /material=MYDISK:[TOTO.DEV] -       ! where to find product material 
     /format=sequential 

This will create a file named IMS-VMS-TOTO-V0100-0-1.PCSI;1


7. Test
=======

Test the kit with the following command:

$ PRODUCT INSTALL TOTO

Please note that the kit file name is IMS-VMS-TOTO-V0100-0-1.PCSI;1 but the 
command to install it is only $ PRODUCT INSTALL TOTO

To install the software on another disk than the default sys$sysdevice disk, use
the /DESTINATION qualifier. 

Example:

$ PRODUCT INSTALL TOTO/DEST=ANOTHER_DISK:[000000.]

Note that the "[000000.]" syntax is *mandatory*.


To log the installation, add the /LOG qualifier.

Example:

$ PRODUCT INSTALL TOTO/DEST=ANOTHER_DISK:[000000.]/log


To watch what happens in terms of accounts creation and modifications, enable 
AUTHORIZATION and FILE ACCESS FAILURE auditing before the installation with the
following commands: 

$ set audit/alarm/enable=authorization
$ set audit/alarm/enable=file_access=failure=all
$ reply/enable


Enjoy.
---

(also posted in http://groups.yahoo.com/group/vmsinstal)