A version changeover refers to the process of installing the BS2000 operating system BS2000 OSD/BC V11.0 using a previous version of the operating system as a working basis:
System installation of the BS2000 operating system can be initiated on a native basis on S or SQ servers with BS2000/OSD-BC V9.0 or higher and then be completed on the relevant Server Unit /390 or x86 of the SE server.
System installation of BS2000 OSD/BC V11.0 can be performed on a native basis on a Server Unit of the SE server with BS2000/OSD-BC V9.0 or higher.
VM2000 guest systems with BS2000/OSD-BC V9.0 or higher are similarly suitable for installation of the BS2000 operating system on all BS2000 servers.
If no BS2000 server with a BS2000 operating system BS2000/OSD-BC V9.0 or higher exists, initial installation is required, see chapter "Initial installation".
System installation is prepared and carried out by systems support. When a version changeover takes place, the BS2000 services can be used in timesharing mode.
During the preparations for a version changeover on the existing BS2000 server, productive operation can be continued using the previous version.
Further prerequisites for the version changeover to BS2000 OSD/BC V11.0 described here:
Installation of the BS2000 operating system on a new pubset
It is possible to initialize magnetic disks in NK mode (SIR or VOLIN, code FORMAT=NK). Pubsets with NK4 disks cannot be used as home pubsets.
A suitable IOCF must be installed for the Server Unit /390 (see chapter "System generation”). Hardware generation (IOCF) with IOGEN 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 on the existing BS2000 server (under TSOS)
Create a new pubset for the BS2000 operating system
Install
BS2GA.MIGRATE V11.0on the current home pubsetCreate and make available a new pubset with a paging area for the new BS2000 operating system
Save the existing user catalog (using the $TSOS.SYSSRPM.BACKUP file on the home pubset) with ARCHIVE
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=*FROM-BACKUP(*ALL)Adjust the user catalog thus created on the new pubset with the PVSREN utility routine (see the “Utility Routines” manual [1]):
//MODIFY-JOINFILE <new_pubset>,<old_home-pubset>,<new_pubset>Install the new BS2000 operating system on the new pubset with IMON
During installation IMON automatically performs the following actions:
Provide and activate the message files and the syntax files
Provide the necessary REP files
Create the DSSM catalog with SSCM
The following installation steps must be executed on the new pubset (only SU /390):
Adapt the size of the BS2000 standard EXEC address space, if necessary. See "Customizing the BS2000 Control System".
Generate the hardware with IOGEN (only necessary in the event of a simultaneous I/O configuration change when transferring to the SE server). See "Rules for generating the I/O configuration data".
Save the IOCF file for transfer to the SVP hard disk of the SE server
The following installation step must be executed with the SIR utility routine:
Create an IPL disk in the new pubset with SIR
(see the “Utility Routines” manual [1]).
Install the customer software for BS2000
Install further BS2000 software products on the new pubset with IMON
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)
Terminate installation preparation
Export the new pubset
If required, transfer from the S or SQ server to the Server Unit /390 or x86
Import the new IOCF to the SVP hard disk of the SE server (for SU /390)
Recable the new pubset for the BS2000 operating system for the Server Unit
Complete installation on the Server Unit /390 or x86 on the SE server
Start the customer system on the new pubset
Bootstrap the customer system
Startup of the BS2000 customer system with DIALOG-Startup (not a first start!)
Load the customer’s network components
Make the user pubsets of the previous version known by means of
/ADD-MASTER-CATALOG-ENTRYSave the customer system
Shut down the customer system / productive operation