Install packages on POSIX

Identification line: [PackageInstallation]

Statement line: <prod>;<imon>;<vers>;<corr>;<uid>;<ipath>

Meanings of the terms in angle brackets:

<prod>	Name of the software package, comprising the product name and optional package names, if the product is split into packages. Syntax: <productname>[:<packagename>]
<imon>	IMON flag, defines whether installation is carried out from within the SCI (Y)or not (N)
<vers>	Product version of the software package: with IMON flag= ’Y' in Vmm.n or mmn format (m,n: digits) or empty with IMON flag= ’N' in mmn format (m,n: digits)
<corr>	Correction status in aso format (a: letter; s,o: digits) The field must remain empty if ’vers' is empty, see Example 1 in the section “The installation program in conjunction with IMON”
<uid>	BS2000 user ID of the archive ID, mandatory for IMON flag= 'N', ignored for IMON flag = 'Y'.
<ipath>	Optional installation path, if the software package supports this. Default value is '/'.

If the IMON flag = 'N', the name of the BS2000 PLAM library which contains the software package is formed as described in the section “Preparing private program packages for installation”.

Example

#
# Batch installation file 
[PackageInstallation]   # install program packages
# <product[:package]>;<imon>;<version>;<corr>;<uid>;<ipath>
#Installation of extended shell with IMON
POSIX-SH;Y
#Installation of NFS without IMON
NFS;N;030;;TSOS
# Installation of C89 with IMON
CPP;Y;;;;/opt/C
# Installation of OPENSSH with IMON
TCP-IP-SV:OPENSSH;Y