Privileges: SUBSYSTEM-MANAGEMENT
Function
The PARK-UNITS statement enables you to park supply units on a user ID (park ID). This statement prepares for the installation of software. At the same time, the delivery is registered in the SCI.
This statement generates a park procedure that is started automatically by IMON if the specified operands are successfully validated.
Parked software can be installed using the INSTALL-UNITS statement by specifying DISTRIBUTION-MEDIUM=*REGISTERED-MEDIUM. As a rule, the parked supply units are deleted after the park ID has been installed (WORK-FILE-DELETING=*YES). The supply units can be retained for a multiple installation.
If the delivery comes with a data volume, the delivery documentation is created and stored in a library.
Format
| PARK-UNITS | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Operands
UNIT-NAME =
Source of supply units to be parked.
UNIT-NAME = *FROM-SOLIS2-DELIVERY(...)
Park supply units from a SOLIS2 delivery.
PACKAGE-NAME = <alphanum-name 1..12>
Package name (as stated in the footer of the delivery contents).
USER-CODE = <alphanum-name 1..8>
User code (as stated in the footer of the delivery contents).
DISTRIBUTION-MEDIUM =
The distribution medium: either IMON uses the information from the SCI or the distribution medium is specified explicitly.
DISTRIBUTION-MEDIUM = *SOLIS2-SUPPORT(...)
The delivery is stored on a data volume shipped with Solis2 (tape cartridge, CD or DVD). All supply units of the specified delivery are available for selection. The delivery information is read from data volume. The selected supply units are copied from data volume to the current user ID and registered in the SCI. Existing files with the same names are overwritten.
VOLUME = <vsn>
VSN of the data volume which contains the delivery (see delivery contents).
DEVICE-TYPE = <device>
Device type of the data volume (see delivery contents).
DOCUMENT-LIBRARY =
Name of the library in which the delivery documentation is stored. If the library already exists, the new delivery documentation is added to it.
DOCUMENT-LIBRARY = *STD
The delivery documentation is stored in the library with the standard name $<work file ID>.<package name>.<customer ID>.DOC where <package name> is the value of the PACKAGE-NAME operand, <customer ID> is the value of the USER-CODE operand and <work file ID> the current file location setting for work files (see the MODIFY-IMON-OPTIONS statement on "MODIFY-IMON-OPTIONS Modify IMON parameter settings ").
DOCUMENT-LIBRARY = <filename 1..54 without-gen-vers>
An explicitly specified library name.
REGISTRATION =
Specifies if the delivery is to be handled as a delivery already registered in the SCI or as a new delivery.
REGISTRATION = *EXTEND
The delivery is handled like a delivery that has already been registered. If there are already entries for this delivery in the SCI, then they are not to be overwritten.
Supply units that have already been parked may not be parked any more.
REGISTRATION = *REPLACE
The delivery is handled like a new delivery. If there are already entries for this delivery in the SCI, then they will be recreated using the information read from the data medium.
Note
All information on previously installed supply units from this delivery will be lost.
DISTRIBUTION-MEDIUM = *LOCAL-SUPPORT(...)
The delivery is stored on a data volume created by the customer (tape cartridge, or virtual volume in a CentricStor). The data volume information of the product movement file is ignored. All supply units of the specified delivery are available for selection. The delivery information is read from data volume. The selected supply units are copied from data volume to the current user ID and registered in the SCI. Existing files with the same names are overwritten.
Restriction/Note:
With LOCAL-VOLUME there is no support of the continuation volume, so the maximum size of a copiable SOLIS2 delivery is limited by the capacity of the LOCAL-VOLUME used.
The maximum necessary size for the delivery may be found on page 4 of the delivery documentation.
Because of the wide range of application options and customer-specific dependencies, conversion of a SOLIS2 delivery to a LOCAL-VOLUME must be performed manually.
Please proceed as described in the example below:
Only when robots are used:
Import the SOLIS2-VOLUME to the foreign cartridge area of ROBAR using the ROBAR-SDF command “ADD-ROBAR-VOLUME” including the ldeclaration of the position in the real archive (e.g. 05)Only when MAREN is used:
Registration of the SOLIS2 VOLUME in the MAREN catalog dFILES FROM=SV,(vsnx),DEVICE=TAPE-C4 SAVE DIR=NONE,TAPES=POOL,DEVICE=TAPE-C4,CH=NO,L=SYSLST END
For multi-tape deliveries, one FILES statement must be specified per tape. vsn1-x are the Volume Serial Numbers (VSN) of the SOLIS2 delivery (see page 1 of the delivery documentation)
- If the delivery is to be copied to a predefined VSN (e.g. when a VSN is reserved using MAREN), the entry in the ARCHIVE job must be changed from “=POOL” to "=POOL" to "=volume number"
Only when robots are used:
Export the SOLIS2-VOLUME from the foreign cartridge area of ROBAR with the ROBAR statement //REMOVE-ROBAR-VOLUME
VOLUME = <vsn>
VSN of the data volume which contains the delivery.
DEVICE-TYPE = <device>
Device type of the data volume.
DOCUMENT-LIBRARY = *STD / <filename 1..54 without-gen-vers>
Name of the library in which the delivery documentation is stored. If the library already exists, the new delivery documentation is added to it. For details refer to the operand description for DISTRIBUTION-MEDIUM=*SOLIS2-VOLUME(...) on "PARK-UNITS Park Software ".
REGISTRATION = *EXTEND / *REPLACE
Specifies if the delivery is to be handled as a delivery already registered in the SCI or as a new delivery. For details refer to the operand description for DISTRIBUTION-MEDIUM=*SOLIS2-VOLUME(...) on "PARK-UNITS Park Software ".
DISTRIBUTION-MEDIUM = *REGISTERED-MEDIUM
The delivery information, the VSN and the device type of the supplied data volume are taken from the open SCI. Files that have already been parked or installed are not read again from the data volume.
It is now possible to install the same supply unit for the same system multiple times using the *REGISTERED-MEDIUM functionality (e.g. after deleting a file of the supply unit by mistake). Moreover, the "Installed" status of a supply unit will now be set only in the SCI of the system where the supply unit is effectively installed and no longer in the SCI from where the installation is triggered (where it remains unchange).
SUPPLY-UNITS =
The supply units to be parked.
SUPPLY-UNITS = *ALL
Park all supply units of the SOLIS2 delivery.
SUPPLY-UNITS = *BY-DIALOG
Select the selection criteria and the associated supply units interactively (see "Interactive selection of supply units" (INSTALL-UNITS Install and register software )).
SUPPLY-UNITS = list-poss(30): <text 1..30 without-sep>(...)
Name of the supply unit, see "Supply unit ".
VERSION =
Version of the supply unit.
VERSION = *HIGHEST-EXISTING
Use the highest version of the supply unit.
VERSION = *ALL
Use all versions of the supply unit.
VERSION = <product-version without-man-corr>
Version designation without the release and correction state.
CORRECTION-STATE =
Correction state of the supply unit.
CORRECTION-STATE = *HIGHEST-EXISTING
Use the highest correction state of the supply unit.
CORRECTION-STATE = *ALL
Use all correction states of the supply unit.
CORRECTION-STATE = *LOWEST-EXISTING
Use the lowest correction state of the supply unit.
CORRECTION-STATE = list-poss(15): <alphanum-name 3..3>
Explicit specification of the correction state of the supply unit. Format: <aso>
TARGET-SYSTEM = *PARAMETERS(...)
Specifications on the target system for which the supply units are to be parked.
VERSION =
BS2000 version of the target system.
VERSION = *CURRENT
Use the current BS2000 version.
VERSION = <product-version without-man-corr>
Explicit specification of the version of BS2000.
Permitted entries: V19.0, V20.0 and V21.0
PUBSET =
HOME pubset of the system for installation.
This specification should only be evaluated if the RMS depot is to be updated (see RMS-DEPOT-UPDATING operand).
PUBSET = *DEFAULT
HOME pubset of the current system.
PUBSET = <cat-id 1..4>
HOME pubset of another target system (foreign system).
OLD-FILE-SAVING =
Save/do not save the files that are overwritten by parking.
OLD-FILE-SAVING = *NO
Do not save the files.
OLD-FILE-SAVING = *WITH-LMS
The files are saved in a library with LMS/LMSCONV .
The name of the save library is $<work file ID>.IMON.SAVE.LIB.<package name>.<customer ID>, where <package name> is the value of the PACKAGE-NAME operand, <customer ID> is the value of the USER-CODE operand and <work file ID> is the current work file ID setting (see the MODIFY-IMON-OPTIONS statement on "MODIFY-IMON-OPTIONS Modify IMON parameter settings ").
OLD-FILE-SAVING = *WITH-ARCHIVE(...)
Save the files with ARCHIVE.
VOLUME = <vsn> / *FROM-OPERATOR(...)
VSN of the data volume to which files are to be saved with ARCHIVE.
VOLUME = *FROM-OPERATOR(...)
The MAREN subsystem automatically chooses the VSN of a free volume. If the MAREN subsystem is not loaded, the statement is rejected with the message IMO0449.
LOCATION = *STD / <alphanum-name 1..8>
Name of the location, from which the free volume will be selected. The default is *STD, i.e. the ARCHIVE backup is carried out with the default settings, without MAREN support.
DEVICE-TYPE = <device>
Device type of the data volume.
RMS-DEPOT-UPDATING =
Transfer/do not transfer the RMS delivery set to the RMS depot.
RMS-DEPOT-UPDATING = *NO
Do not transfer the RMS delivery set to the RMS depot.
RMS-DEPOT-UPDATING = *PARAMETERS(...)
Transfer the RMS delivery set to the RMS depot.
DEPOT-LOCATION = *STD
Use the RMS depot with the standard file name <catid>$<userid>.RMS.DEPOT, where <catid> is the catalog ID of the pubset of the target system (see PUBSET operand) and <userid> is taken from the delivery information.
DEPOT-LOCATION = <partial-filename 2..18>
The RMS depot with the :<catid>:$<userid>. specified in DEPOT-LOCATION and the standard file name RMS.DEPOT are used.
FILE-LOCATION = <partial-filename 2..16>
The location at which the release items are to be parked.
Notes
Work files
After the supply units have been successfully parked with no errors, IMON generates a cleanup procedure for the park ID that contains all DELETE-FILE commands for deleting the parked supply units. The park ID can be cleaned using this procedure after the installation of the park ID has been completed:
$<park ID>.IMONDEI.PRK.<name of the supply unit>.<package name>The statement is rejected and an error message is displayed in the following cases:
The user ID specified as the saving location for work files using WORK-FILE-LOCATIONS in the MODIFY-IMON-OPTIONS statement cannot be accessed.
The user ID specified as the saving location using FILE-LOCATIONS cannot be accessed or has a memory overflow.
DISTRIBUTION-MEDIUM=*REGISTERED-MEDIUM was specified, but the SCI does not contain a SOLIS2 delivery with the specified package name and user code.
The delivery information does not exist or cannot be accessed:
DISTRIBUTION-MEDIUM=*REGISTERED-MEDUM is specified, but the delivery information file does not exist or cannot be accessed.
DISTRIBUTION-MEDUM=*SOLIS2-VOLUME/*LOCAL-VOLUME is specified, but the specified data volume or the specified device does not exist or cannot be accessed, or the delivery information file cannot be copied from tape to the current user ID.
The delivery information cannot be processed successfully by IMON.
The target system version is not [V]19.0, [V]20.0 and [V]21.0
Execution of the park order is aborted if:
The user ID specified as the storage location cannot be accessed or has a memory overflow.
A data backup with LMS was requested, however LMS/LMSCONV cannot be accessed.
A data backup with ARCHIVE was requested, however ARCHIVE cannot be accessed.
A file that was already parked cannot be overwritten (because it is locked).
If DISTRIBUTION-MEDIUM=*LOCAL-VOLUME the delivery has already been saved on another data volume (e.g. virtual volume of a CentricStor). In this case, the specified VSN and device type are used for access to the installation files and the entries in the product movement file are ignored. However, only files from the specified volume can be processed.
In a heterogeneous disk environment (K and NK disks), the same storage location must be used for work files (WORK-FILE-LOCATION) when installing the park ID as for parking. IMON requires a few work files which were created when parking in order to generate the installation procedure.