Application Unit (AU)
Component of the SE server; with the help of the SE Manager, enables central, web-based management of customer applications. An AU permits operation of applications under Linux, Windows, VMware or other hypervisors.
AU
CSR
See Configuration Save and Restore (CSR).
Configuration disk
Internally mirrored disk of the Unit (MU, SU x86, HNC) where the data of the SE server configuration are locally stored. In addition to the internal configuration disk, up to two external configuration disks can be configured on external FC RAID systems, to which all MUs and SU x86 have access via a redundant connection.
Configuration Save and Restore (CSR)
Sichert die Konfigurationsdaten der Management Unit in einem Archiv. Das Sicherungsarchiv enthält alle Konfigurationsdaten, die der Kunde über den SE Manager selbst verwaltet.
Data Network Private (DANPR)
Private data network for use as SE server-internal private customer network. When required, you can configure up to 99 networks DANPR<n> (with <n>= 01..99).
Data Network Public (DANPU)
Public data network for connecting applications to the public customer network.You can configure up to 8 networks DANPU<n> (with <n>= 01..08).
DANPR
See Data Network Private (DANPR).
DANPU
See Data Network Public (DANPU).
FDDRL job
For each FDDRL function statement, one FDDRL job is defined per single or pubset disk. Another FDDRL job is defined per disk set. Each FDDRL job can be handled either under the calling task (FDDRL maintask) or under a separate task (FDDRL subtask).
FDDRL subtask
FDDRL jobs can be processed by a subtask generated by FDDRL.
HAL
See Hardware Abstraction Layer (HAL).
Hardware Abstraction Layer (HAL)
Firmware component on SU x86 for mapping privileged /390 interfaces to the basic machine code. This mapping is required, for example, when handling exceptions, managing memory and also for system diagnostics.
HNC
High Speed Net Connect
HNC implements the connection from an SU /390 to a LAN. HNC designates both the Linux-based basic software which is integrated into the SE Manager and the hardware unit on which this basic software runs. As a hardware unit, the HNC is a component part of the Net Unit on SE servers which have an SU /390.
Initial Program Load (IPL)
First phase of system initialization after booting. IPL reads in the CLASS1-EXEC, system parameters, and REPs.
IOCF
See IO Configuration File (IOCF).
IO Configuration File (IOCF)
Contains information on the configuration of the input/output devices of an SU /390. The IOCF must be installed in the service processor.
IORSF
Input/Output Resource File
An IORSF contains a BS2000 device configuration, which is required to start up an SU /390.
IPL
See Initial Program Load (IPL).
KVP
Console distribution program
Access to a BS2000 console window takes place via a KVP (console distribution program).
The KVP performs the following tasks, among others:
Authorization checks
Distribution of the BS2000 tasks to multiple console windows
Short- and long-term storage of the console communication logs (KVP logging)
BS2000 sees a KVP as two (emulated) KVP devices (or a device pair) which are identified by their mnemonic names.
Management Admin Network Public (MANPU)
Public management network for the administrative access to MU, BS2000 systems and AUs.
Management Control Network Local (MCNLO)
Private management network for the local SE server communication
Management Control Network Private (MCNPR)
Private management network for the SE server communication
Management Optional Network Private (MONPR)
Private management network for the SE server communication. When required, you can configure up to 8 additive networks MONPR<n> (with <n>= 01..08).
Management Optional Network Public (MONPU)
Public management network, which can be configured as the additive administration network when required (e.g. when AIS Connect is not to be operated via MANPU but over a separate network).
Management SVP Network Private (MSNPR)
Private management network, which enables the SVP communication to the SU /390 on SE700/SE500.
Management Unit (MU)
Component of the SE server; with the help of the SE Manager, enables central, web-based management of all units of an SE server.
MANPU
See Management Admin Network Public (MANPU).
MCNLO
See Management Control Network Local (MCNLO).
MCNPR
See Management Control Network Private (MCNPR).
MONPR
See Management Optional Network Private (MONPR).
MONPU
See Management Optional Network Public (MONPU).
MSNPR
See Management SVP Network Private (MSNPR).
MU
See Management Unit (MU).
Net client
Implements access to Net-Storage for the operating system using it.
In BS2000/OSD the net client, together with the BS2000 subsystem ONETSTOR, transforms the BS2000 file accesses to corresponding UNIX file accesses and executes these using NFS on the net server.
Net server
File server in the worldwide computer network which provides storage space (Network Attached Storage, NAS) for use by other servers and offers corresponding file server services.
Net-Storage
The storage space provided by a new server in the computer network and released for use by foreign servers. Net-Storage can be a file system or also just a node in the net server's file system.
Net Unit
Component of the SE server; enables an SE server to be connected to customer networks (LAN/SAN). The Net Unit incorporates High Speed Net Connect (HNC).
Parallel Access Volume (PAV)
Multiple I/O requests can be executed simultaneously to a logical volume. A logical PAV volume is represented by a basic device and up to seven alias devices.
PAV
See Parallel Access Volume (PAV).
SE Manager
Web-based user interface for SE servers. The SE Manager runs on the Management Unit and permits central operation and administration of Server Units (SU /390 and SU x86), Application Units (x86), Net Unit (including HNC), and the storage.
SKP
service and console processor
An SKP enables servers with /390 architecture to be operated, the connected devices to be managed, and remote service to be supported.
The term SKP is used in the three views hardware functionality, software functionality, and device type:
Hardware functionality
To operate, S servers require an SKP as a Hardware Unit. The SKP Hardware Unit SKP is a PRIMERGY server which has a local console, a Host Controller, and various ports for LAN connection and supporting remote service.
On the SE server the Management Unit (MU) provides this hardware functionality for operating SU /390.
Software functionality
On an SKP Hardware Unit the SKP Manager provides the SKP functionality for operating the S server and managing the devices and remote service.
On the SE server the SKP functionality is integrated into the SE Manager.
Device type
In BS2000 an SKP device type is used (e.g. SKP2).
Server Unit /390 (SU /390)
Component of the SE server; Server Unit with /390 architecture. A /390-based Server Unit (SU /390) enables operation of BS2000 (Native BS2000 or VM2000).
Server Unit x86 (SU x86)
Component of the SE server; Server Unit with x86 architecture. An x86-based Server Unit (SU x86) enables operation of BS2000 (Native BS2000 or VM2000). XenVM operation with Linux or Windows guest systems is also possible as an option.
SVP
service processor
SVP clock
Autonomous clock which supplies the TODR with the real time at system startup. In SU /390 the SVP clock is part of the SVP. In SU x86 the SVP clock is emulated via the basic software X2000.