Initial installation

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  V21.0A 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 of BS2000 V21.0A described in this section applies to X2000/M2000  V6.4 and higher.

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.

1. Boot the emergency system (BS2000 V21.0A) 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

2. During the system startup the interactive mode is also started, therefore no further commands are mecessary. After the system startup, console and dialog operation are possible via the SE Manager.
   
   

3. Only for SU /390
   On the basis of  your configuration, use the IOGEN utility 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) transfer the already generated IOCF to the BS2000 system. The new 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].
   The IOCF (the IORSF file) can alternatively also be generated via SE Manager and transferred to the SVP hard disk. A running BS2000 system is not required for this. A more detailed description can be found in chapter "Generating the IO configuration data (IOCF) at the SE Manager" and in the "Operating and Managing" manual [5].

4. Only for SU /390
   Shut down the emergency system.
   Perform an IMPL , activate the new IOCF and boot the emergency system .

5. Use the SIR utility routine to create a pubset, see the “Utility Routines” manual [1].

6. Use IMON to install the software (SOLIS deliveries) for the BS2000 operating system and the system-related software on the  pubset.

   During installation with IMON, all files are installed on the pubset and made ready for activation at the next BS2000 startup ).

   During installation IMON automatically performs the following actions, among others:

   • Provide and activate the message files and the syntax files

   • Provide the necessary REP files

   • Generate the DSSM catalog with SSCM

7. If you are using the BS2000 operating system for the first time, adapt the following files on the pubset to the requirements 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

8. Only for SU /390
   If necessary, you can 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 system.

9. Terminate the emergency system with shutdown.

10. Perform a startup of the  new system.

    • Perform the IPL of the  created pubset.

    •  Activate the network configuration with the adapted SOF file for regular dialog operation. 

    • Make already existing pubsets available with the commands /ADD-MASTER-CATALOG-ENTRY and /IMPORT-PUBSET.

    • If necessary, use the SIR utility routine (see the “Utility Routines” manual [1]) to create additional pubsets. Make these pubsets available using /IMPORT-PUBSET [ACTUAL-JOIN=*FIRST,...].

    • Set up the required entries in the user catalog in the various pubsets.

    •  Make a Backup from the system.

    •  Shut down the BS2000 system or continue productive operation.