S/390 Microprocessor Complex Configuration
S/390 Microprocessor Complex Configuration (Type 8641)
After the S/390 Microprocessor Complex has been successfully initialized, the S/390 Configuration program can be
accessed by clicking on the 390 (370) Configuration Icon in the System/390 (System 370) Group on the OS/2 Desktop.
(See 'System/390 Icons')
The Configuration program is a menu driven program that provides two main functions.
- It allows you to describe the mapping between the input/output (I/O) devices available on the PC Server
System/390 and the System/370 I/O devices they emulate. See 'Device Map'
- It provides an easy way for Virtual Machine/Enterprise Systems Architecture (VM/ESA) users to create and
maintain new VM userids on the PC Server System/390 and minidisk associated with these userids.
Changes are made to the system configuration by changing the values in the data menus.
The following example of reading a 9336 DASD summarizes how the 370 I/O subsystem emulates I/O operations
on the PC Server System/390.
- The 390 operating system does a system I/O instruction to real device 100.
- The 390 Licensed Internal Code (LIC) passes all I/O instructions to the 370 I/O subsystem
running on the PC Server Processor Complex.
- The 370 channel emulator executes the 370 channel program and passes the request to the device
manager that claims that range of devices in DEVMAP. In this example, it would be an fixed block
architecture (FBA) device manager.
- The FBA device manager gets the request for device 100. It looks in the DEVMAP entry for device 100
to fill out the OS/2 file name for 9336 device 100. The device map points to the OS/2 file that emulates the
370 disk drive, for example, D:\VM\MAINT.191 for a VM system or D:VSDISRES.140
for a virtual storage extended (VSE) system.
- A request is issued to OS/2 to read the data from the OS/2 file name MAINT.191 in the \VM directory of disk drive D:
or from the OS/2 file name DOSRES.140 in the \VSE directory of disk drive D:\
- OS/2 issues the request for the data to the PC Server device containing disk drive D:
- The data is passed back up the line until it is presented to the requesting VM or VSE program.
The Configurator requires the following four files to operate correctly. (For information on the content of these files,
refer to the Introducing the PC Server 500 System/390L manual (Form Number GC24-5717-00) supplied with the computer.
- DEVMAP.xxx
- DMKRIO.ASM
- DMKSYS.ASM
- USER.DIR
Back to 
Please see the LEGAL - Trademark notice.
Feel free - send a 
for any BUG on this page found - Thank you.