In a customer-specific installation, the entire delivery or only a part thereof is stored on the home pubset or on another, imported pubset. In contrast to a default installation, in a customer-specific installation the depot location and activation mode can differ from the default.
Parking and single or multiple installation from the park ID is also considered to be a type of customer-specific installation, whereby installation from the park ID itself can be carried out as a default installation.
System environment and requirements for the customer-specific sample
installations
The following settings and requirements are valid for the customer-specific installations described on pages 123 (Installation on the home pubset with customizing ) through 191 (Example with SDF statements ). The first table lists the general system environment and the features of the SOLIS2 delivery.
Current system | MM.N |
Target system of the installation | MM.N |
Package name of the SOLIS2 delivery | <package-name> |
Customer identifier | SOL2P |
Data volume identifier | QE6171 |
Device type | TAPE-C4 |
Supply units contained | EDT, OPENFT, OPENFT-CR, PERCON, SORT |
MM.N - current version
The next two tables detail the differences between the IDs and file names for an installation on the home pubset, an installation where the supply units are first parked, and a multiple installation.
For an installation on the home pubset
Catalog ID of the home pubset | I29A |
Standard SCI | :I29A:$TSOS.SYS.IMON.SCI |
Default system ID | TSOS |
Work file ID | SYSSAG on the home pubset |
Path name for work files | :I29A:$SYSSAG. |
Library for the supply documentation | :I29A:$SYSSAG.<package-name>.SOL2P.DOC |
Backup library | :I29A:$SYSSAG.IMON.SAVE.LIB.<package-name>.SOL2P |
Installation procedure | :I29A:$SYSSAG.<package-name>.<time-stamp>.IE |
Log for important message files | :I29A:$SYSSAG.<package-name>.IC |
Installation log | :I29A:$SYSSAG.<package-name>.<time-stamp>.IL |
Modified installation ID for the EDT and PERCON supply units | OSID1 (instead of the default system ID TSOS) |
Modified location of the RMS depot | :I29A:$OSD6 |
Handling of earlier subsystem versions | Entries from earlier versions remain in the DSSM catalog |
For an installation where the supply units are first parked
Catalog ID of the home pubset | I29A |
Standard SCI | :I29A:$TSOS.SYS.IMON.SCI |
Park SCI (foreign SCI for parking) | :I29A:$PARKSW1.SYS.IMON-PARK.SCI |
Default system ID | TSOS |
Work file ID | PARKSW1 on the home pubset, with WORK prefix |
Park ID | PARKSW1 on the home pubset |
Path name for work files | :I29A:$PARKSW1.WORK. |
Library for the supply documentation | :I29A:$PARKSW1.<package-name>.SOL2P.DOC |
Backup library | :I29A:$PARKSW1.WORK.IMON.SAVE.LIB.<package-name>.SOL2P |
Park procedure | :I29A:$PARKSW1..WORK.<package-name>.<time-stamp>.PE |
Log for important console messages | :I29A:$PARKSW1.WORK.<package-name>.IC |
Park log | :I29A:$PARKSW1.WORK.<package-name>.<time-stamp>.PL |
For multiple installations (of parked software)
Catalog ID of the home pubset | I29A |
Standard SCI | :I29A:$TSOS.SYS.IMON.SCI |
Park SCI (foreign SCI for parking) | :I29A:$PARKSW1.SYS.IMON-PARK.SCI |
Default system ID | TSOS |
Catalog ID of the imported pubset | 6A0B |
Default system ID for the installation on the imported pubset | TSOS |
Work file ID | PARKSW1 on the home pubset, with WORK prefix |
Park ID | PARKSW1 on the home pubset |
Path name for work files | :I29A:$PARKSW1.WORK. |
Backup library | :I29A:$PARKSW1.WORK.IMON.SAVE.LIB.<package-name>.SOL2P |
Installation procedure | :I29A:$PARKSW1.WORK.<package-name>.<time-stamp>.IE |
Log for important console messages | :I29A:$PARKSW1.WORK.<package-name>.IC |
Installation log | :I29A:$PARKSW1.WORK.<package-name>.<time-stamp>.IL |
The <time-stamp> part of the name is the timestamp of the installation in the format <month><day><time><year>, where
<month> <day> <time> <year> | is the first three letters of the month is a one or two-digit day of the month is the time at which the installation started in the form hhmmss is a four-digit figure |
General steps in a customer-specific installation (parking also)
| Depending on the call, IMON branches to menu mode or waits for SDF statements. | |
| The standard SCI $TSOS.SYS.IMON.SCI on the home pubset is opened implicitly (in the SDF mode when started, in menu mode when the delivery is opened). If a foreign SCI is to be created/written, it must be opened explicitly. This procedure is presented in section | |
| IMON creates work files on the home pubset under the SYSSAG user ID by default. | |
| ARCHIVE reads the data volume. Information on the package name, user code, VSN, and volume type from the accompanying information is needed during this process. A delivery that is already open can be opened as a registered delivery. | |
| All supply units are offered for further processing by IMON, confirm this selection with [DUE] To install or park parts of the delivery only, modify the selection accordingly and confirm it with [DUE]. When a registered delivery is opened, all supply units not yet parked or installed are offered for further processing. | |
| The option 4 (Install) for installing the selected supply units is preset in the Edit menu once you select the supply units in menu mode. | |
| The default parameter file SYSPAR.IMON.LAST of the current environment is preset. If this file exists, IMON uses the specific installation parameters stored there as defaults in the subsequent dialog boxes | |
| The operating system version and the home pubset of the active system are preset. | |
| The depot location (installation or park ID) is adapted to the customer’s requirements. (Placement: part of the customizing process) | |
| The activation parameters are adapted to the customer’s requirements. (Activation: part of the customizing process) This point is omitted if the supply units are parked. | |
| IMON generates and starts the installation or park procedure. It either loads all of the files in the supplied products to your specified location and registers them in the SCI as installation units or the products are registered in the SCI as supply units with the status “parked”. | ||
| The SOLIS2 delivery is closed explicitly if IMON is to be used again (e.g. to check the SCI). Otherwise IMON can be terminated directly. | |
| If the SOLIS2 delivery was not already closed, it is closed implicitly when IMON is terminated. | |
| Any necessary postprocessing and the order in which it should be carried out can be found in the delivery information. This point is omitted if the supply units are parked. | |
The subsequent installation from the park ID can be carried out as an default installation or a customer-specific installation.
The schematic representation of the sequence can be found on "Customer-specific installation on the home pubset with customizing " (for the home pubset with customizing), "Customer-specific installation with prior parking " (for installation with parking) or "Sequence of a customer-specific multiple installation of a previously installed delivery " (for a multiple installation).