A version changeover refers to the process of installing the BS2000 V21.0 using a previous version BS2000 OSD/BC V10.0 or V11.0 .
If no suitable system with BS2000/OSD-BC V10.0 or higher exists, initial installation is required, see chapter "Initial installation".
System installation is prepared and carried out by systems support.
During the preparations for a version changeover , productive operation can be continued using the previous version.
Further prerequisites for the version changeover to BS2000 V21.0
Installation of the BS2000 operating system on a new pubset
Type D3435 disk storage devices in K or NK2 format are required for the new pubset.
A suitable IOCF must be installed for the Server Unit /390 (see chapter "System generation”). Hardware generation with IOGEN or SEM at the MU need only be executed if the I/O configuration is changed.
No hardware generation is required for the Server Unit x86.
The sequence of steps involved in a version changeover is detailed in the following sections.
Installation preparation (under TSOS)
- Create a new pubset with a paging area for the new BS2000 operating system using the SIR utility
Install the package BS2OS.MIGRATE V1.0 supplied with SOLIS on the current home pubset, as described in the SOLIS delivery letter
Save the existing user catalog (using the $TSOS.SYSSRPM.BACKUP file on the home pubset) with ARCHIVE
- Make the new pubset available:
/IMPORT-PUBSET … Read in the SYSSRPM.BACKUP file on the new pubset with ARCHIVE
Export the new pubset
Import the new pubset again with
/IMPORT-PUBSET ..., RECONSTRUCT-USERCAT=*BY-BACKUP(SCOPE=*ALL)Adjust the user catalog thus created on the new pubset with the PVSREN utility routine (see the “Utility Routines” manual [1]):
//MODIFY-JOINFILE PUBSET=<new_pubset>,DEFAULT-CATID=<old_home-pubset>,NEW-DEFAULT-CATID=<new_pubset>
Installation of the operating System
The new BS2000 operating System is installed on the new pubset using the IMON utility program. To do this, follow the instructions in the delivery letter from SOLIS for the respective package.
Prepare the new pubset for initial operation
Create an IPL disk in the new pubset with SIR as decribed in the SOLIS delivery letter (see the “Utility Routines” manual [1]).
- Install further software required for the operation
Create the customer-specific files on the new pubset (job scheduler, SOF file for BCAM, CMDFILE, startup parameter file, ACS catalog, GUARDS catalog etc. for SECOS, HSMS/ARCHIVE directories, MAREN catalog, etc.)
- For SU /390 you can adapt the size of the BS2000 standard EXEC address space, if necessary. See "Customizing the BS2000 Control System".
Completion of the installation
Export the new pubset
Bootstrap the customer system on the new pubset with DIALOG-Startup (not a first start!)
Load the network components
Make the required user pubsets known by means of
/ADD-MASTER-CATALOG-ENTRYSave the customer system
Shut down the customer system / productive operation