Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

System generation on Server Unit /390

&pagelevel(3)&pagelevel

Because the I/O configuration data and the BS2000 Control System have been separated, the following objects can be generated:

  • a file containing the I/O configuration data (IOCF – I/O Configuration File) with the IOGEN utility routine (hardware generation)

  • a BS2000 Control System adjusted to the address space (based on the BS2000 standard EXEC)

Generating the I/O configuration data

Initial installation or a change to the I/O configuration requires (new) generation of the I/O configuration data (hardware generation) with the IOGEN utility routine, see "Generating the I/O configuration data (IOCF) with IOGEN". IOGEN generates the I/O configuration file (IOCF), which defines the entire I/O configuration.

IOCF files can also be created directly in the SE Manager without running BS2000 and transferred to the SVP.

A hardware generation is not required for a version changeover if the I/O configuration remains unchanged.

Disk controllers and/or disk devices can be exchanged under certain circumstances without requiring a hardware generation, see "Disk device configuration".

The I/O configuration (channels, controllers, devices) can be modified during operation (dynamic I/O configuration change), see "I/O configuration".

Customizing the BS2000 Control System

BS2000 Standard EXECs are available on all hardware architectures. A BS2000 control system adjusted to the address space can be generated using the procedure supplied, see the section "Customizing the BS2000 Control System".

A customer’s own system modules can be defined and loaded as DSSM subsystems.