A new SE server is prepared by the manufacturer so that it is ready for use by the customer. The Server Units are delivered with a pregenerated and preinstalled emergency system. The emergency system is IPL-capable. It is intended for installation and maintenance only and should not be used for everyday operation.
If the emergency system cannot run, it will be created anew by customer support while BS2000 is operating.
If a version changeover of the BS2000 operating system is not possible, you can use the emergency system to perform an initial installation.
The initial installation of the BS2000 OSD/BC V11.0 operating system is prepared and executed by the BS2000 systems support for the required Server Unit.
The DVD drive on the Management Unit (MU) can be used here as an emulated tape device, see note 4 of "Device type table".
Please refer to the manuals for SE servers.
The initial installation described in this section applies to X2000/M2000 V6.2 and higher.
An initial installation of BS2000 OSD/BC V11.0 on SU /390 under X2000/M2000 below V6.2 is not supported. In that case, BS2000 OSD/BC V10.0 has to be installed using FIRST. After that, a version changeover to BS2000 OSD/BC V11.0 has to be performed.
Conducting the initial installation
The initial installation of BS2000 is almost identical for SU /390 and SU x86. See the following instruction for the necessary installation steps. These steps have to be carried out in the same order as described. Instructions specific to only one type of Server Unit are identified as such.
Boot the emergency system using the basic configuration.
SU /390: mnemonic: CCF0, device number CCF0
(the emergency system contains a suitable standard IOCF)SU x86:mnemonic D0, device number 0130
Establish the local dialog mode via the BCAM command
/DCSTART DCSOF=SYSDAT.BCAM.SE.SOF. If you use the standard command file,CMDFILE.BS2000, the command will be executed automatically.Only for SU /390
On the basis of the customer configuration, use the IOGEN utility routine to generate a customer IOCF (IO configuration file, see "Rules for generating the I/O configuration data") or (if this has already been done elsewhere) read in a tape containing this file. The new customer IOCF has to include the basic configuration of the supplied standard IOCFs with the devices of the MU (consoles, LOCLAN, emulated discs and tapes).
This step can be omitted (e.g. after a disk crash) if a valid IOCF still exists on the SU. The SU /390 cannot run without a suitable IOCF.The IOCF can be stored on the SVP hard disk using
/WRITE-IOCF, see the “Commands” manual [2].Only for SU /390
Shut down the emergency system.
Perform an IMPL and boot the emergency system using the customer configuration.Use the SIR utility routine to create a customer pubset, see the “Utility Routines” manual [1]. The pubset with the emergency system can be kept as a stand-by pubset or for diagnosis.
Use IMON to install the software for the BS2000 operating system and the system-related software (SOLIS delivery) on the customer pubset.
During installation with IMON, all files are installed on the customer pubset and made ready for activation the next time BS2000 is started).
During installation IMON automatically performs the following actions:
Provide and activate the message files and the syntax files
Provide the necessary REP files
Generate the DSSM catalog with SSCM
When first using the BS2000 operating system, you have to adapt the following customer specific files on the customer pubset manually to the specifications of your data center:
startup parameter file
command file (CMDFILE)
user catalog entries
remote data processing files (SOF file)
SJMSFILE
ACS catalog
GUARDS catalog (if the SECOS software product is used)
HSMS/ARCHIVE directories
MAREN catalog
Parameter files of other software
Only for SU /390
If necessary, you can manually adapt the size of the BS2000 standard EXEC address space (see "Customizing the BS2000 Control System"). The BS2000 standard EXEC can also be changed in the finalized customer system.Shut down the emergency system.
Perform the startup of the customer system.
Perform the IPL of the customer pubset.
Establish the regular dialog mode for the customer network configuration with the adapted SOF file.
Make existing customer pubsets available using
/ADD-MASTER-CATALOG-ENTRYand/IMPORT-PUBSET.If necessary, use the SIR utility routine (see the “Utility Routines” manual [1]) to create additional customer pubsets. Make these pubsets available using
/IMPORT-PUBSET [ACTUAL-JOIN=*FIRST,...].Create the entries in the user catalog in the various pubsets.
Save the customer system.
Shout down the customer system or continue productive operation.