IBM P 390, R 390 User Manual

International Technical Support Organization	SG24-4847-00

P/390 and R/390 with OS/390: An Introduction

August 1996

IBML	International Technical Support Organization	SG24-4847-00

P/390 and R/390 with OS/390: An Introduction

August 1996

Take Note!

Before using this information and the products it supports, be sure to read the general information under Appendix B, ªSpecial Noticesº on page169.

First Edition (August 1996)

Comments may be addressed to:

IBM Corporation, International Technical Support Organization

Dept 541 Mail Station P099

522 South Road

Poughkeepsie, New York 12601-5400

When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.

© Copyright International Business Machines Corporation 1996. All rights reserved.

Note to U.S. Government Users Ð Documentation related to restricted rights Ð Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

3.1 PC Server System/390 OS/390 Installation

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	vii
How This Redbook Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . .	vii
The Team That Wrote This Redbook . . . . . . . . . . . . . . . . . . . . . . . .	viii
Comments Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	viii
Chapter 1. Product Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . .	1

1.1Functional Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2P/390 Microprocessor Complex . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2.1Channel Emulator and Device Managers

1.2.2Starting the P/390 Subsystem - Overview

. . . . . . . . . . . . . . . . .	7
. . . . . . . . . . . . . . . . .	9

1.3PC Server System/390 System . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.4RISC/6000 S/390 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.4.1RISC/6000 S/390 (Model 7012-390) . . . . . . . . . . . . . . . . . . . . . 13

1.4.2RISC/6000 S/390 (Model 7013-591) . . . . . . . . . . . . . . . . . . . . . 14

1.5Support Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

1.6Adapters and Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

1.7OS/390 on CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

1.8Positioning and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

1.8.1Selecting a System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 2. Configurations and the P/390 Configurator . . . . . . . . . . . . . .		23
2.1	Server Workload Considerations (P/390) . . . . . . . . . . . . . . . . . . . .	23
2.2	PC Server System/390 Configurations . . . . . . . . . . . . . . . . . . . . .	24
2.3	RISC/6000-591 S/390 Configurations . . . . . . . . . . . . . . . . . . . . . . .	29
2.4	3270 Connection Configurations - Overview . . . . . . . . . . . . . . . . . .	30

2.5Tape Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

2.6The P/390 Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 3. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

. . . . . . . . . . . . . . . . . . . 43

3.1.1Hardware Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.1.2OS/2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.1.3CM/2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.1.4P/390 Support Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.1.5OS/390 CD-ROM Installation . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.2IPL and Use MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3.3 RISC/6000 S/390 OS/390 Installation . . . . . . . . . . . . . . . . . . . . . . 50

3.3.1Hardware Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

3.3.2AIX Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

3.3.3P/390 Support Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

3.3.4OS/390 CD-ROM Installation . . . . . . . . . . . . . . . . . . . . . . . . . 54

3.3.5IPLing OS/390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

3.4Expanding the CD-ROM Systems . . . . . . . . . . . . . . . . . . . . . . . . 58

3.5	Working With the P/390 Configurator . .	. . . . . . . . . . . . . . . . . . . .	59
3.6	Non-RAID Installation (PC Server) . . . .	. . . . . . . . . . . . . . . . . . . .	63
3.7	Installing Other MVS or OS/390 Systems	. . . . . . . . . . . . . . . . . . . .	64
3.7.1 Creating and Initializing Disk Volumes		. . . . . . . . . . . . . . . . . .	65
Chapter 4. Device Managers and Commands		. . . . . . . . . . . . . . . . . . .	69

4.1Starting Device Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

4.2Device Managers for DASD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

© Copyright IBM Corp. 1996

iii

4.2.1AWSCKD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

4.2.2AWSFBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

4.3 Device Managers for Simple Terminals . . . . . . . . . . . . . . . . . . . . 75

4.3.1AWS3274 (P/390) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

4.3.2AWS3274 (R/390) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

4.3.3LAN3274 (P/390 only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

4.4Device Managers for Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . 82

4.4.1AWSTAPE Device Manager . . . . . . . . . . . . . . . . . . . . . . . . . 82

4.4.2SCSI34x0 and AWS34x0 . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

4.4.3 ISITAPE Device Manager (P/390 Only) . . . . . . . . . . . . . . . . . . . 89

4.5Device Managers for Unit Record . . . . . . . . . . . . . . . . . . . . . . . . 90

4.5.1AWS2540 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

4.5.2AWS2821 Device Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 92

4.5.3AWS3215 Device Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 96

4.6 Device Managers for Communications . . . . . . . . . . . . . . . . . . . . . 96

4.6.1LAN3172 Device Manager (P/390) . . . . . . . . . . . . . . . . . . . . . 97

4.6.2LAN3172 Device Manager (R/390) . . . . . . . . . . . . . . . . . . . . . 99

4.6.3WAN3172 Device Manager (P/390) . . . . . . . . . . . . . . . . . . . . 100

4.6.4WAN3172 Device Manager (R/390) . . . . . . . . . . . . . . . . . . . . 101

4.6.5LCS3172 Device Manager (P/390) . . . . . . . . . . . . . . . . . . . . 101

4.6.6LCS3172 (R/390) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

4.6.7MGR3172 (P/390 OS/390 Only) . . . . . . . . . . . . . . . . . . . . . . 104

4.6.8	AWSICA Device Manager (P/390 Only) . . . . . .	. . . . . . . . . . .	105
4.6.9	AWSPBS Device Manager (Normally VM and VSE)	. . . . . . . . . .	106

4.7Other Device Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

4.7.1AWSC370 Device Manager . . . . . . . . . . . . . . . . . . . . . . . . 106

4.7.2	LAN3088 Device Manager (P/390 only) . . . . . . . . . . . . . . . . .	110
4.7.3	AWS2703 Device Manager (P/390 only) . . . . . . . . . . . . . . . . .	110
4.7.4	AWSOMA Device Manager (P/390 only) . . . . . . . . . . . . . . . . .	112
4.7.5	AWSPCSRV (VM Only) . . . . . . . . . . . . . . . . . . . . . . . . . . .	113
4.7.6	AWSMOUNT Command (P/390 and R/390) . . . . . . . . . . . . . . .	113

4.7.7AWSSTAT (P/390 only) . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

4.7.8AWSSTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

4.7.9AWSPROF Command (P/390) . . . . . . . . . . . . . . . . . . . . . . . 116

4.7.10CLRIO Command (P/390) . . . . . . . . . . . . . . . . . . . . . . . . . 116

4.7.11AWSCFG Commands (P/390) . . . . . . . . . . . . . . . . . . . . . . . 116

4.7.12DEV2NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

4.7.13IPL Command (P/390) . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

4.7.14ipl390 Command (R/390) . . . . . . . . . . . . . . . . . . . . . . . . . 117

4.7.15LTRENAME Command (P/390 Only)

4.7.16RDEVMAP Command (P/390 Only)

. . . . . . . . . . . . . . . . . . .	118
. . . . . . . . . . . . . . . . . . .	118

4.7.17BLDLIST Command (P/390) . . . . . . . . . . . . . . . . . . . . . . . 118

4.7.18C370MAP Command (P/390) . . . . . . . . . . . . . . . . . . . . . . . 119

4.7.19AWSCMLT Command (P/390) . . . . . . . . . . . . . . . . . . . . . . 119

4.7.20TRCC370 Command (P/390) . . . . . . . . . . . . . . . . . . . . . . . 119

4.8Other Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Chapter 5. Other Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

5.1S/390 Manual Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

5.2Diagnostic Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

5.3Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

5.4XTAPE Product (P/390 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 131

5.5OS/390 Device Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

5.6Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

5.7OS/2 and Hardware Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

iv P/390 MVS

5.8	System/390 Activity Window . . . .	. . . . . . . . . . . . . . . . . . . . . .	136
5.9	Device Manager Letters and Names	. . . . . . . . . . . . . . . . . . . . .	137

5.103270 Emulator Keyboards . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

5.11Writing a Device Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

5.12Send and Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

5.13Backing Up OS/390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

5.14 OS/390 Performance and Capacity (P/390) . . . . . . . . . . . . . . . . . 140

5.15tn3270 Emulators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

5.15.1xant 3270 Emulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

5.15.2hcon 3270 Emulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

5.16AWSICA and BSC NJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

5.17Internet Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

5.18LAN Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Chapter 6. Frequent Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

6.1PC Server System/390 Systems . . . . . . . . . . . . . . . . . . . . . . . . 155

6.2RISC/6000 S/390 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

6.3Questions Common to Both Bases . . . . . . . . . . . . . . . . . . . . . . 158

Appendix A. AWS2821 Translation Table (P/390) . . . . . . . . . . . . . . . .		167
Appendix B. Special Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . .		169
Appendix C. Related Publications . . . . . . . . . . . . . . . . . . . . . . . . .		171
Appendix D. How To Get ITSO Redbooks . . . . . . . . . . . . . . . . . . . . .		173
D.1	How IBM Employees Can Get ITSO Redbooks . . . . . . . . . . . . . . .	173
D.2	How Customers Can Get ITSO Redbooks . . . . . . . . . . . . . . . . . .	174
D.3	IBM Redbook Order Form . . . . . . . . . . . . . . . . . . . . . . . . . . .	175
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .		177

Contents v

vi P/390 MVS

Preface

This document introduces the IBM PC Server System/390 (commonly known as the P/390), with special emphasis on its use with OS/390. The discussion also includes the IBM RISC/6000 with S/390 Server on Board (commonly known as the R/390), but in less detail. The emphasis is on understanding the nature of these products, with their advantages and limitations. The reader is assumed to be a technical professional, with an MVS background. Typical configurations are described. Installation is described, briefly, as it is covered in detail in other documents. A small amount of observed performance data is included.

(181 pages)

This replaces an earlier redbook MVS and the IBM PC Server 500 System/390, GG24-2538. The general discussion context is for a system used for programming development, and suitable configurations are described for this purpose. The reader is assumed to have a system programmer′s knowledge of OS/390 or MVS. This document is not an introduction to OS/390. It is an introduction to OS/390 running on the PC Server System/390 or the RISC/6000 S/390.

How This Redbook Is Organized

The descriptions in this document correspond with Version 2.1 of the P/390 support programs, level 4.0.0.1 of the R/390 support programs, and the IBM S/390 Developers′ Association version of OS/390 on a CD-ROM. Later updates and releases may change some details, but the basic comments and recommendations should remain valid.

You should have PC Server 500 System/390: Installation, Configuration, and User′s Guide for MVS/ESA, SA22-7210-1, and PC Server 500 System/390: Messages and Codes, SA22-7227, before installing your P/390 MVS system. These documents contain detailed installation instructions. You should also have the redbooks Connectivity on a PC Server System/390, SG24-4624, and Printing with MVS on the IBM PC Server System/390,

SG24-4612, for more information in these areas.

The first chapter of this document describes the products concepts and positioning, and describes the general operation of the products.

The second chapter describes the variety of configurations that can be used, and how the P/390 configuration utility is used.

The third chapter describes, briefly, the steps required to install a system -- from Server hardware to OS/390.

The fourth chapter provides detailed information about the various device managers provided with the P/390 support programs.

The fifth chapter contains discussions of a number of areas related to OS/390 operation. A limited amount of performance information is provided.

The sixth chapter lists many frequently asked questions about these products, with associated answers.

© Copyright IBM Corp. 1996

vii

The Team That Wrote This Redbook

This document is the result of work in the International Technical Support

Organization at the Poughkeepsie Center. The author was Bill Ogden.

We extend thanks to the following people for substantial assistance in producing this document:

∙

∙

∙

∙

∙

∙

∙

∙

Chuck Berghorn - IBM P/390 Development (Poughkeepsie)

Bohdan Demczar - IBM Development (Poughkeepsie)

Marty Ziskind - IBM P/390 Development (Poughkeepsie)

Louis Voerman - IBM P/390 Development (Poughkeepsie)

Carmine Castaldo - IBM R/390 Development (Poughkeepsie)

Joel Naslow - IBM P/390 Development (Poughkeepsie)

Doris Conti - IBM Development (Poughkeepsie)

Gordon Chamberlain - Interprocess Systems, Inc. (Roswell, Georgia)

Comments Welcome

We want our redbooks to be as helpful as possible. Should you have any comments about this or other redbooks, please send us a note at the following address:

[e-mail]

Your comments are important to us!

viii P/390 MVS

Chapter 1. Product Descriptions

The products discussed in this document are built around a single adapter card, the S/390 Microprocessor Complex. This adapter is often referred to as the P/390 adapter, and is explained in some detail in 1.2, ªP/390 Microprocessor Complexº on page 4. The adapter is part of several products, one based on an IBM PC Server and two based on RISC/6000 systems.

To avoid writing ªPC Server or RISC/6000 systemº hundreds of times throughout this document, we will refer to a generic ªServerº in any discussion that applies to both PC Server and RISC/6000 based products. This usage ignores the common distinction between workstations and servers, and is solely for the purpose of this document. We elected not to use the word ªhostº for the PC Server or RISC/6000 base system. Although it is a more logical word, it is very firmly associated with mainframes, and could be especially confusing in a document dealing with OS/390 and MVS.

The proper names for the products are IBM PC Server S/390 and IBM RISC/6000 with System/390 Server On Board. They are often referred to as P/390 and R/390 systems, respectively, although these names are not strictly proper, and may confuse the adapter card with the total system.1 The key portion of the names, ªS/390,º indicates the unique nature of the products. With proper setup of the underlying Server systems, they provide System/390 environments. OS/390 (MVS), VM, and VSE, with all their subsystems and applications, will run on these systems -- with very few limitations.

We will use the term ªOS/390º to mean both OS/390 and any reasonably current release of MVS. For the purposes of this document, there is no distinction between OS/390 and MVS. This document is about P/390 OS/390; much of what is discussed also applies to VM and VSE systems, but they are not the subject here and are seldom mentioned. Also, as a final note on terminology, we will use ªstorageº rather than ªmemoryº for P/390 storage2 .

We will reference the document P/390 & R/390: OS/390 New Owner′s Cookbook, SG24-4757, a number of times and simply refer to it as the Cookbook. It contains brief, specific instructions for some of the basic administrative tasks needed with OS/390. The descriptions are based on the S/390 Developers′ Association OS/390 CD-ROM system, which is described later in this document. (The Cookbook is scheduled to be available in late 1996.)

The P/390 adapter contains a S/390 processor. It does not emulate or simulate a S/390 processor, it is a S/390 processor. While it is a S/390 processor, it is not a S/390 I/O subsystem. The underlying Servers are used to emulate3 the I/O subsystem and a selected set of S/390 I/O devices. Most of this document, as

1Thus a ªP/390 systemº could be either a PC Server or a RISC/6000 system, with the ªP/390º referring to the S/390 adapter. In another context, ªP/390º may refer to the PC Server S/390 system, in contrast to an R/390 system. The context of a discussion usually indicates which meaning is implied.

2Memory and storage are the same thing, but mainframe terminology is usually ªstorageº and PC/RISC terminology is usually ª m e m o r y º

3Some documents imply subtly different meanings for the words ªsimulateº and ªemulate.Thisº document is not so sophisticated, and arbitrarily uses the word ªemulateº when describing the functions of the P/390 support programs.

© Copyright IBM Corp. 1996

1

well as other redbooks dealing with these products, is concerned with this emulation of S/390 I/O functions.

There are differences between these systems and a S/390 mainframe, but these differences are generally outside the normal operating system and application program interfaces. The differences include:

∙System partitioning into multiple system images (ªLPARsº) is not available.

∙Multiprocessor functions are not available.

∙Shared DASD, with a mainframe or another P/390 OS/390 system, is not available (at the time this was written).

∙IOCDS configuration functions are not used. These are replaced by (simpler) I/O configuration controls through an OS/2 or AIX program, and a file known as DEVMAP.

∙Integrated communications I/O, as found on IBM 9370 and 9221 systems, is emulated through various Server drivers. Not all integrated communications functions are emulated. (OS/390 does not support these integration communication adapters for VTAM use. OS/390 can use them as basic bisync devices, such as JES2 might use, but this is no longer common and is not formally supported.)

∙Sysplex connections are not supported.

∙Parallel bus and tag channel connections are available, using a S/370 channel adapter card and a driver program on Servers. Only certain devices are supported through this path. In particular, DASD connections are not supported at this time.

∙ESCON channel connections are not available at this time.

∙Integrated console attachments (such as used on IBM 4381, 9370, and 9221 systems) are not supported. The Server provides a 3270 emulator which operates as though an IBM 3174 control unit were attached. The emulator provides multiple 3270 sessions, and can be used for both console and user sessions.

∙Expanded storage functions are supported. You can partition the S/390 storage into standard and expanded storage. However, there is a one-to-one tradeoff between standard and expanded storage, and most users elect to use full standard storage and no expanded storage.

In addition to emulating a S/390 I/O subsystem, the Server uses P/390 adapter interfaces to initiate IPLs, perform various S/390 resets, and provide most S/390 operator functions -- such as register and storage displays.

A package of P/390 support programs must be installed in the Server to provide the I/O emulation and console functions for programs executing in the P/390 adapter. These P/390 support programs are a key part of the complete products. (In keeping with the slightly confusing terminology that exists for these products, P/390 support programs are used to support the P/390 adapter, which is used in both P/390 and R/390 systems. There are two packages of P/390 support programs: one for P/390 systems and one for R/390 systems.)

2 P/390 MVS

1.1 Functional Flow

The functional flow shown in Figure 1 is very important in understanding these systems, and we suggest you take time to understand the concepts involved. While the figure is a high-level abstraction, it represents a Server with a P/390 adapter, running an OS/390 application. Two processors are indicated: the left side (in the figure) is the S/390 processor, and the right side is the Server processor (a Pentium or RISC processor). Each ªsideº has its own storage. The processors do not share storage. For OS/390, the P/390 adapter will normally have 128 MB storage; the size of Server memory will vary, but it will have at least 32 MB.

In the figure, an OS/390 application is executing -- this means it is executing S/390 instructions, just as though it were running on a mainframe. At the same time, the Server can be executing its own workload4. The flow of control might go like this:

∙The OS/390 application encounters an I/O function, such as a GET macro.

∙This passes control to an access method. The access method may construct a channel program and issue an EXCP request (or something similar) to OS/390. For example, this might be a read operation for a 3380 disk at S/390 address 120. As far as OS/390 is concerned, it thinks it has a ªrealº 3380 at this address.

∙OS/390 gets control, schedules the channel program, and eventually issues an SSCH5 instruction. Up to this point, operation has been exactly the same as mainframe operation.

∙The SSCH instruction works differently than on a mainframe. It constructs several control blocks, in control storage not visible to OS/390, and causes an interrupt in the Server system.

Figure 1. Conceptual Flow of Control

4We will discuss the practicalities of additional Server workloads later.

5Start Subchannel. This is the modern equivalent of the original SIO (Start I/O) instruction in the S/360.

Chapter 1. Product Descriptions

3

∙A P/390 support program (running under OS/2 or AIX) gets control (based on the interrupt from the P/390 adapter).

∙It gives control to the P/390 channel emulator program. As its name implies, this program emulates many of the functions of a S/390 channel. It sustains a number of parallel operations in the ªchannel,º permitting OS/390 to have multiple outstanding I/O operations. It interprets portions of CCWs, and provides initial condition codes for SSCH instructions.

∙The channel emulator determines which device type and address are involved (a 3380 disk at address 120, in this example, based on the definitions in a DEVMAP that is not shown), and gives control to a device manager program. At the same time, it usually returns initial status to the P/390, completing the SSCH instruction. The P/390 continues executing S/390 instructions, running in parallel with the emulation programs on the Server. In the Server, a DEVMAP (device map) is used to relate S/390 addresses (such as 120) to particular device managers (such as the one used to emulate a 3380 disk). The DEVMAP is maintained by the P/390 configurator program (operating on the Server), and is remotely similar to the IOCDS of a mainframe. The DEVMAP is described in considerable detail later.

∙The P/390 support programs include many device managers, for different types of devices. In general, a device manager emulates a particular type of ªrealº mainframe device6. In this example, the particular device manager (which would be the AWSCKD.EXE program for a P/390 system) emulates a 3380 disk drive.

∙The device manager uses a real Server I/O device, and issues normal READ/WRITE instructions through OS/2 or AIX to access the device. The device manager calls the channel emulator, as needed, to transfer data to/from P/390 storage. The channel emulator does not need to interrupt the P/390 to do this; it can access P/390 storage by using a movable window that is accessed from the Server side.

∙When the device manager completes the requested function, it notifies the channel emulator. The channel emulator then causes an I/O interruption in the P/390, and creates a CSW (channel status word) with appropriate indicators, such as channel end and device end.

While the analogy is not exact, the P/390 channel emulator functions much as a mainframe channel does, and P/390 device managers tend to perform the functions of mainframe control units.

1.2 P/390 Microprocessor Complex

This section provides slightly more detail about the system. None of this material is necessary for system use, but it may help you become more comfortable with general concepts. The S/390 processor card used is shown in Figure 2 on page 5. It is a Micro Channel adapter card. The S/390 processor is a single chip on the card. The processor has approximately 220K gates and uses 420 signal pins of the 647-pin mount. (The other pins are used for power and grounds.) It has 32KB of control storage and uses horizontal microcode with 136 bits per word. Internal data flow is 64 bits wide.

6 This is not exactly the case when a S/370 Channel Emulator/A adapter is used, but this is described later.

4 P/390 MVS

Figure 2. P/390 Processor Complex Adapter

The basic P/390 adapter has 32 MB storage. When a daughter card is used (to add 96 MB additional S/390 storage), the storage is interleaved.7 The 32MB storage on the S/390 processor card is not the ªfirst 32MB.º We assume the additional 96 MB is always used when OS/390 is used. The daughter card requires a Micro Channel slot; it uses the slot for power and ground connections, but does not transfer data through the Micro Channel.

The P/390 adaptor contains its own timing circuits, and its clocking is independent of the Server. The current P/390 contains a 71 MHz clock that is divided into a four-phase clock of approximately 17.7 MHz. Different S/390 instructions require different numbers of clock cycles to complete, but the average performance is approximately 4.5 S/390 processor MIPS.

An important design goal was to avoid any modifications to OS/390 (or any other S/390 operating system used with the system). The key to doing this was to move all I/O operations to the OS/2 side of the system. No modifications are required for OS/390 to run on this system, although some reconfiguration may be appropriate.

The S/390 microprocessor is a single chip. It is controlled by microcode that is loaded when the P/390 subsystem is started.8 The S/390 processor (through hardware and microcode) implements the full S/390 subchannel architected interfaces; that is, a S/390 program can issue all the defined I/O instructions and work with the control blocks associated with these instructions. The subchannel control blocks (as used in all System/390 platforms) are the link between the S/390 processor and the OS/2 support programs.

When the S/390 program (usually OS/390′s IOS code) issues an SSCH instruction (Start SubChannel), an interrupt is generated for the OS/2 side of the processor. The OS/2 code (part of the I/O subsystem provided on the P/390 diskettes) can

7Two different daughter cards were originally available, one with 32 MB and one with 96 MB. The 32 MB card (which brought the total P/390 adapter to 64 MB) is no longer available.

8The microcode is included on the P/390 support diskettes.

Chapter 1. Product Descriptions

5

access S/390 memory and can ªseeº the ORB, CCWs, I/O areas, and so forth, that are associated with the I/O operation. A combination of OS/2 code and P/390 microcode maintains SCHIBs that correspond to emulated subchannels.9

An IOCDS is not used. An equivalent mapping operation (and an IOCDS is essentially a map) is built from the DEVMAP file you build with the P/390 subsystem configurator function.10 There is a single path to each emulated device.

The S/390 processor is a full System/390 ESA processor. It executes S/390 instructions as its native instruction set. In addition:

∙All of the ªESAº and ªXAº instructions (such as Branch and Save) are present.

∙Extended instructions are available, including string instructions, square root, cancel I/O, compression, expanded sorting, move inverse, move page(2), PER-2 and extensions, private space, data spaces, ACL protection, address limit checking, broadcast purging, subspace group, compare until substring equal, incorrect length indication suppression, set address space control fast, storage protection override, suppression on protection, and so forth.

∙Some ªassist microcodeº is present, including Interpretive Execution (Interception format 2, PER extensions, VM data space, Storage-Key functions), add FRR, SVC assist, Obtain/Release Local Lock, Obtain/Release CMS lock).

∙Low address protection, fetch protection override, and public storage key control are supported.

A few other considerations are:

∙Emulated disks (3380s, for example) do not have a ªCEº track. They need to be initialized as though they were minidisks. (Both the stand-alone ICKDSF program and the OS/390 version do this.)

∙In general, diagnostic CCWs are not fully processed. The intention is that all ªrealº device recovery is done by the OS/2 programs, and OS/390 will see only successful I/O operations or simple failures (ªdevice not ready,º for example). OS/390 will not be called upon to issue complex I/O diagnostic operations. IBM S/390 I/O maintenance tools may not work correctly (and should not be used).

∙Obscure sense bits are not emulated.11

∙Older devices, potentially attached through a S/370 Channel Emulator/A adapter, have not been tested.

∙The S/370 Channel Emulator/A adapter does not support ªRead Backwardº commands. (These commands were used by the SORT program, in conjunction with 3420 tape drives, many years ago. The only current usage of read backwards that we have encountered is with OS/390 standard label processing; special-case code is included to handle this usage.)

9See the S/390 Principles of Operation manual for definitions of these terms.

10Suitable DEVMAPs are included with the various operating system releases on CD-ROM that are intended for use with these systems.

11For example, a real 3420 tape drive has a sense bit that indicates that the ªleft reel is turning.º

6 P/390 MVS

∙There is no hardware support for 2K storage keys; only 4K keys are supported. (VS1 used 2K keys.)

The P/390 subsystem provides several trace functions. By using the Trace icon, trace data can be displayed or sent to a file. There are two trace types:

1.Kernel trace, that records all S/390-Server interactions

2.Device trace, that records only interactions associated with a specific emulated device

The normal trace table (this is the P/390 subsystem trace table, which has no relation to the OS/390 trace table) has 2000 entries. It is most useful for debugging emulated I/O problems.

1.2.1 Channel Emulator and Device Managers

To a certain extent, the P/390 support programs are structured like mainframe hardware. The CPU and central storage communicate with channels, the channels communicate with control units, and the control units work with devices. In our case, the AWSCHAN.EXE (using the P/390 module names for these examples) program is the channel. On one side, it works with CPU interrupts, I/O requests, and storage, and on the other side it works with control units, emulated or real.

The AWSCKD.EXE device manager program is an example of an emulated control unit. Real control units can be attached through the S/370 Channel Emulator/A adaptor, although the AWSC370.EXE module is needed to interface the channel (AWSCHAN) to the adapter. The Server system and devices, to some extent, correspond to the end devices that are managed by control units. The analogy with mainframe hardware is not exact, but it is close enough to help understand the general design of the P/390 support programs.

Like a mainframe channel, AWSCHAN supports multiple concurrent activities between the CPU and various control units. A mainframe channel is often limited to eight control units, while AWSCHAN has no fixed limit to the number of device managers (emulated control units) it can manage. It is limited to 255 total devices, as seen by the P/390 configurator (which is described later).

AWSCHAN provides handling of all S/390 I/O instructions, initial handling of all CCWs, manages all accesses between device managers and the S/390 main storage12, and manages all I/O interrupts sent to the S/390. It general, it handles many parallel functions. Internally, it uses a fixed number of buffers to pass data to/from device managers and S/390 storage. AWSCHAN is both a very complex module, and a key module for P/390 support, and its developers have continually refined and improved it. Some of these improvements account for the dramatic performance improvements included in Version 2.1 of the P/390 support programs.

The key improvements were in handling (emulated) PCI13 functions. OS/390 program fetch, which involves reading program text and relocation information from disk, and relocating programs as they are placed into main storage, is

12 There are a few exceptions to this, in which other programs or adapters directly access S/390 storage, but these exceptions do not negate the general design.

13 Program Controlled Interruption. This is a flag in a CCW that causes the channel to interrupt the CPU when operation for that CCW is started. The channel continues to process the CCW and the rest of the channel program. After receiving the interrupt,

Chapter 1. Product Descriptions

7

much faster if PCI is fully used. The same changes in AWSCHAN also improved the processing of partitioned data set directories. These two areas, PCI fetch and PDS directory processing, are two of the most important underlying functions for OS/390 performance.

The device managers are the key to emulating S/390 devices. A device manager has these characteristics:

∙It emulates a device and its control unit.

∙It interprets CCWs and performs whatever OS/2 I/O is required to emulate the requested I/O.

∙It generates sense data as required.

∙It may emulate multiple devices (such as multiple 3380 drives) and multiple device types (such as 3380 and 3390).

∙It may (or may not) be multithreaded. A few major device drivers (such as AWSCKD for the P/390) are multithread, with one thread for each emulated device.

∙Some serialization may be enforced to allow orderly operation by the device manager code.

∙Each device manager decides how it wants to handle overlap of multiple devices. Complex drivers (such as AWSCKD) provide as much overlap as possible (and are usually limited by the underlying Server I/O design and devices).

There is no requirement for a device manager to use multiple threads; the managers for the R/390 generally do not use threads while many P/390 managers do use threads. Figure 3 shows the basic threads of a simple device manager for a P/390 base. The main line code receives an initial I/O request and provides initial status (so the SSCH instruction can complete). Final status (when the emulated I/O operation is complete) is provided by the back-end code (and thread). Asynchronous functions (such as an attention interrupt) are handled by the async code and thread.

The support programs have several interfaces to the S/390 processor card:

1.Interrupts (both ways).

2.Shared Memory. The Server can read S/390 storage through a movable window. Either real or virtual addresses can be used.

3.A communications buffer (on the adapter card). This buffer contains ICBs (interrupt control blocks) and SCHIBs (subchannel information blocks).

4.Manual operations functions such as alter/display, IPL, stop, start, and so forth.

The SSCH operation is the primary link between S/390 code and the supporting P/390 subsystem. The complete process, using the channel emulator and device manager, goes like this:

1. OS/390 issues an SSCH instruction to start an I/O operation.

the CPU can dispatch a program that processes data received from the channel thus far. The CPU could also chain additional CCWs, depending on the data obtained earlier, to the channel program.

8 P/390 MVS

Figure 3. General Thread Structure for Device Manager

2.P/390 microcode moves data to the SCHIB, completes a ICB, and interrupts the Server.

3.The P/390 router gets control and passes control to the P/390 channel support program.

4.The channel module:

a.Checks if the correct device manager is available

b.Checks the emulated device state

c. Releases the S/390 with C C = 0 (if the device state warrants it)

d.Routes the SSCH request to the device manager

5.The device manager:

a.Validates the CCW

b.Passes initial status to the channel

c. Interprets the CCWs, performs Server I/O, emulates CCW chaining, provides PCI interrupts, and so forth

d. Returns final status to the channel

The timing characteristics of this process do not exactly match the characteristics of a mainframe. If programs follow correct coding practices (and all the major MVS products do, as far as we know) there are no problems. If a program modifies CCWs too soon, there could be incompatibilities. Good program design calls for using PCIs before modifying active CCW chains, and this works properly.

1.2.2 Starting the P/390 Subsystem - Overview

When the Server system is booted, the P/390 adapter is idle. The Server must load P/390 microcode and then use control instructions to start P/390 processing. There is no requirement to use the P/390 adapter, of course. A user can boot OS/2 or AIX and use it normally. The P/390 adapter becomes active only when the appropriate commands are issued to start it. The P/390 functions are useful only when a S/390 program is available (on disk or tape) to execute. The S/390 program to be executed is normally the operating system (OS/390), but it could be a standalone program such as ICKDSF or a tape-to-disk restore program.

Chapter 1. Product Descriptions

9

The P/390 functions are normally started with the IPL.CMD REXX command procedure. (The ªIPL P/390º icon issues this command internally.) The startup operation goes like this:

1.Issue the IPL.CMD command (usually by clicking on an icon).

2.IPL.CMD starts AWSMAIN (one of the P/390 support programs).

3.AWSMAIN, among other things:

a.Loads the S/390 processor microcode (if it is not already loaded)

b.Loads the current DEVMAP.

c.Starts AWSCHAN (to begin emulated channel operations)

d. Builds SCHIBs to correspond to devices defined in the DEVMAP.

4.Start all the device managers. Each manager will decide (by inspecting the DEVMAP details) whether it is needed.

5.Wait for the device managers to initialize.

6.Issue an IPL function to the S/390 processor.

7.The S/390 processor executes an SSCH instruction to the I/O address specified in the IPL function.

8.The I/O operation is emulated by the appropriate device manager.

9.Control is given to the program instructions read by the initial I/O operation.

10.Operation continues, and OS/390 (or whatever was selected) loads itself.

1.3PC Server System/390 System

The original P/390 (announced mid-1995) used a PC Server 500 as the base. The current P/390 (announced mid-1996) uses a PC Server 520 as the base. Characteristics include:

∙CPU - a 133MHz Pentium (The PC Server/500 had a 90Mhz Pentium.)

∙Memory - 32MB (default) to 256MB 70 ns, 2-way interleaved on a 64-bit interface. ECC error detection and correction is standard.

∙Six Micro Channel and two PCI slots are included. (The Server 500 had eight Micro Channel slots.)

∙Two serial ports and two parallel ports

∙A SCSI adapter is standard, on the mother board. (The Server 500 did not have this.)

∙An SVGA adapter is standard, on the mother board. (The Server 500 did not have this.)

∙Enclosure - 18 disk bays (!), up to 38GB internal disk storage (with combinations of 1 inch, HH, and FH drives), 434 watt power supply, variable speed fans, lockable media door, tamper-evident covers, LogicLock (C2 functionality), message LED, and other features.

∙Systems intended for P/390 use include:

−A fast/wide SCSI RAID adapter with two or three channels. (The Server 500 RAID adapter had two channels.)

−A 4mm tape drive and a CD-ROM drive.

−Five 2.25 GB fast/wide disk drives

Early experience with the PC Server 520 indicates that the faster Pentium processor leaves more capacity available for OS/2 work (while OS/390 is also running). It does not cause OS/390 to run significantly faster, although we expect it will allow more effective parallel usage of disk drives.

10 P/390 MVS

Figure 4. Basic PC Server System/390 for OS/390. This is the base configuration of a system intended for use with OS/390. Use with OS/390 implies that the additional P/390 memory ªdaughter cardº is installed, and five 2.25

GB disk drives are installed. Later versions of the P/390 may use the planar SCSI adapter for the 4mm tape and the CD-ROM drive.

This basic system, as shown in Figure 4, leaves four Micro Channel slot and one PCI slot available for additional adapters. One potential disk bay slot may be lost in providing a SCSI connection for the 4mm tape drive, depending on the internal connections selected. The two lower disk bays can each be used for six thin (one inch high) disk drives, or three half-high disk drives. All disks must be mounted in hot swap trays. (Note that the integrated SCSI adapter, on the planar board, could also be used to drive the CD-ROM and 4mm tape drive since both this adapter and these devices use 8-bit SCSI interfaces. Production systems, built after this was written, may use this method.)

The RAID adapter controls the first bay of disk drives (five or six drives) and possibly the CD-ROM and 4mm tape drive. It has one or two more channels. The second channel is used for another bank of internal disk drives. The third channel can be used for yet another bank of internal disk drives, or for external SCSI devices. In general, the planar SCSI adapter would be the first choice for external SCSI connections.

Using the two lower disk bays requires two backplanes (into which the hot swap trays connect) and one additional power supply. You can order these when your initial system is built, or you can order them later.

A large number of configurations are possible, based on this initial configuration. Several of these are described in Chapter 2, ªConfigurations and the P/390 Configuratorº on page 23. The base configuration, as shown in the figure, is completely sufficient for OS/2 and has sufficient disk space to emulate 3380 drives to load and run OS/390, with space for DLIBs, CICS, DB2, work volumes,

Chapter 1. Product Descriptions

11

and a reasonable amount (a double-capacity 3380 drive, for example) of data space. The server display is used for up to five 3270 sessions, including one for the OS/390 console.

The supported operating system is Warp Server. In this case, supported means that IBM will accept problems reported on the system. A substantial number of systems are known to be using Warp Connect, although this is not officially supported.

The base Server system includes 32 MB memory, and this is sufficient for use with the P/390 subsystem. More memory should be considered if there will be significant Server memory use in parallel with P/390 activity.

The planar board provides an SVGA adapter. A display must be ordered. Use of the P/390 functions is not dependent on any particular display size or resolution, however we strongly recommend using a good quality 17-inch display in 1024x768 mode. Normal P/390 utilization will have several 3270-emulation windows open, and this becomes marginal on smaller displays or with lower resolution.

The P/390 support programs emulate certain DASD devices for OS/390 to use. The emulated DASD uses large files on normal OS/2 disks. These OS/2 disks are in either FAT or HPFS format.14 We recommend using HPFS for your OS/2 disk partitions that will contain emulated volumes. FAT partitions cannot exceed 2 GB; you will be working with much more space than this15, and attempting to use FAT partitions may cause unnecessary disk fragmentation or reloading of emulated volumes.

1.4 RISC/6000 S/390 Systems

Two R/390 systems based on RISC/6000 units are available. One is intended as an entry system, and the other as a high-end production system. Both use AIX as the Server operating system. AIX Version 4.1 (or later) is required. Earlier releases are not supported as bases for R/390 systems.

The configurations for the R/390 are not as standardized as is the PC Server P/390. Especially for the larger model, a wide range of disk configurations, display adapters, LAN adapters, and so forth, is possible. The S/390 functions place no unique requirements on the RISC/6000 base, other than two Micro Channel adapter slots for the P/390 adapter (and additional storage), and sufficient disk space for OS/390.

14FAT is the disk format used by DOS and Windows. It is named after the File Allocation Table that it uses to manage files. The High Performance File System is unique to OS/2. OS/2 supports both file systems. A disk partition is formatted with one or the other. In general, FAT disks are used for compatibility with DOS, since DOS can work with a FAT disk but not an HPFS disk. HPFS disks (partitions) are used when DOS compatibility is not needed. HPFS has advantages in allocation granularity, fragmentation control, and error recovery.

15A single emulated 3380-K volume is about 1.8 GB.

12 P/390 MVS

Figure 5. Basic RISC/6000 S/390 System (Model 7012-390)

1.4.1 RISC/6000 S/390 (Model 7012-390)

This system is based on the desk-top model 390.16 The basic configuration is indicated in Figure 5. Key characteristics are:

∙

∙

∙

∙

∙

∙

∙

∙

67 MHz POWER2 processor

32 MB memory standard, with 512 MB maximum

80 MB/sec Micro Channel, with four slots

Integrated SCSI-2 dual-port fast/wide adapter

Integrated Ethernet adapter

Two internal disk bays

CD-ROM drive

4mm tape drive (optional, but required for R/390)

A display must be ordered for the system. We recommend a 17-inch unit with at least 768x1024 or 1024x1024 resolution. Normal R/390 utilization will involve several 3270-emulation windows (under X Windows) and a smaller screen, or one with less resolution will impact usability.

This system, the RISC/6000-390 S/390, is not recommended for use with OS/390. The configuration shown does not have sufficient S/390 storage (there is only the 32 MB on the P/390 adapter) or disk space for OS/390. This system is intended for use with VM or VSE. It could be upgraded to run OS/390, by adding the S/390 96 MB storage daughter card, and by changing the disks to larger ones or by adding external disks. This would tend to create a ªmaxed outº system suitable only as an entry-level OS/390 platform.

16 The presence of the characters ª390º in the base RISC model name is just a coincidence. The 7012-390 systems were in use before the S/390 adapter and functions were added to it.

Chapter 1. Product Descriptions

13

1.4.2 RISC/6000 S/390 (Model 7013-591)

This is a larger system, with more adapter slots and more disk bays. A general outline is shown in Figure 10 on page 30. Characteristics include:

∙

∙

∙

∙

∙

∙

∙

∙

∙

77 MHz POWER2 processor, with 256KB data cache

64 MB memory standard, with 2 GB maximum

80 MB/sec Micro Channel, with eight slots

Integrated SCSI adapter

SCSI-2 dual-port fast/wide adapter (uses one MC slot)

Six internal disk bays (3.5 inch, half high)

CD-ROM drive

Standard display adapter

4mm tape drive (optional, but required for R/390)

A display must be ordered, and the same considerations apply as for the 7012-390.

1.5 Support Programs

The P/390 adapter is useless without the P/390 support programs, which are usually delivered on a set of diskettes. (There are two sets of diskettes: one for the PC Server and one for RISC/6000 Servers.) A number of components are included:

∙The channel emulator, already mentioned, and a number of programs involved in interrupt handling and routing

∙

∙

∙

∙

∙

∙

A considerable number of device managers

Configurator programs, support programs, and tables

Microcode for the P/390 adapter, and a program to load it

Operator functions for the P/390 adapter

Window functions and icons for OS/2 or AIX

Documentation files for the various device managers, and one or more READ.ME files

∙

∙

Trace tools

Various other utility functions, which typically operate as OS/2 or AIX commands.

The use of many of the support programs is centered around the configuration program. This is the program that defines the mapping of OS/390 devices (a 3380 volume, for example) to the device managers and files used under OS/2 or AIX to emulate the devices. You will frequently use this program while setting up your system, and installing OS/390. This program is also used for systems running VM and VSE; some of the functions are specific to those operating systems. Use of the configurator is described in more detail in 2.6, ªThe P/390 Configuratorº on page 36.

Another key support area provides console (IPL, stop/start, reset, storage display, and so forth) functions for the S/390 processor. (These functions are

14 P/390 MVS

provided through the ªManual Operationsº icon in the ªP/390º window.) Some of these functions are described in more detail in 5.1, ªS/390 Manual Operationsº on page 121.

The device managers are used to emulate various mainframe I/O devices. The device managers that are relevant to OS/390 are discussed, in detail, in Chapter 4, ªDevice Managers and Commandsº on page 69.

Device Manager Names

For the P/390 system, most device managers have names beginning with the letters AWS, although a few have other names. For the R/390, there is more variation in the device manager names. The following tables always show the P/390 name, followed by the R/390 name in parenthesis, if it is different. The R/390 configurator panel, described in detail later, uses the same names as the P/390. Internally, it then translates these names to the appropriate R/390 module names. For this reason, we almost always refer to the P/390 device manager names throughout this document. The only time you, as a system administrator, would see the R/390 module names is if you list the contents of the directory containing the modules or if you edit the R/390 IPL or STOP scripts.17

Do not assume that R/390 and P/390 device managers have exactly the same characteristics because they have the same names. In some cases the equivalent P/390 and R/390 device managers are essentially the same code (within the limits of porting between OS/2 and AIX), but in other cases the underlying code is totally different. Briefly, the device managers include:

∙AWSCKD (dmckd) - CKD DASD emulator, used to emulate 3380, 3390, 9345, 3375, 3350, and 3330 disk drives.

∙AWSFBA (dasd) - FBA DASD emulator for 3370, 3310, 0671-4, 9332, 9335, 9336-10, FB-512 devices.

∙AWSC370 (dmhuron) - S/370 channel adapter manager, used with the S/370 Channel Adapter/A card to attach ªrealº control units and devices. Only a limited set of control units and devices are usable through this attachment.

∙AWSTAPE (dmtape) - 3803 3420/3422 emulator, which uses Server files for tape volumes.

∙SCSI3420 (dm34xx) - uses 4mm or other SCSI-attached tape drives to emulate an IBM 3420 drive.

∙SCSI3480 (dm34xx) - uses 4mm or other SCSI-attached tape drives to emulate an IBM 3480 drive.

∙AWS3420 - is a second copy of the SCSI3420 device manager, permitting the use of a second SCSI-attached tape drive as a 3420 device.

∙AWS3480 - is a second copy of the SCSI3480 device manager, permitting the use of a second SCSI-attached tape drive as a 3480 device.

∙AWS2821 (printer) - Printer emulator, which emulates an IBM 2821/1403 printer, with output directed to a Server file or to a printer port.

∙AWS2540 (dm2540) - Card reader emulator, uses Server files to emulate input from a card reader.

17 The R/390 module names are different for backward compatibility with a previous system. The module names may be changed in a later release to match the P/390 names.

Chapter 1. Product Descriptions

15

∙AWS3215 (dm3215) - Console keyboard emulator, used to emulate an IBM 3215 typewriter/keyboard. Some stand-alone utility functions (S/390) may require this, and it can be used by VM.)

∙AWS3274 (dm3270) - IBM 3274 (non-SNA) control unit emulator, which provides several 3270 sessions on the Server display terminal. For P/390, it uses a special interface from CM/2. For R/390, it uses TCP/IP tn3270 sessions.

∙LAN3172 (dm3172) - IBM 3172 LAN gateway (SNA), provides an SNA gateway for external OS/2, DOS, and Windows systems (usually with 3270 emulation programs) to communicate with OS/390. It can also be used for SNA connections to a mainframe or to other SNA devices such as printers. LAN3172 replaces an older device manager, AWS3172. References to AWS3172 are automatically mapped to LAN3172.

∙WAN3172 - Provides SDLC connections for VTAM

∙LAN3088 - IBM 3088 CTC emulation over a LAN, used only between multiple P/390 (OS/390, VM, or VSE) systems. (Not available for R/390.)

∙AWSICA (sdlcdm) - Integrated Communications Adapter (ICA) support for SDLC (not with OS/390) and BSC.

∙AWSPBS - Provides BSC and SDLC links using Portmaster adapters

∙LAN3274 - Permits LAN (non-SNA) 3270 emulation sessions, using a simple (NetBios or TCP/IP) protocol. These sessions appear as local (coax-attached) 3270 units to OS/390. LAN3274 does not exist for R/390, where AWS3274 provides similar functions.

∙LCS3172 (lcs3172tx, lcs3172rx) - Provides an interface similar to a IBM 3172 Channel Station for TCP/IP interfaces.

∙MGR3172 - Provides NetView connectivity to emulated 3172 devices running LAN3172 or WAN3172.

∙AWSTFA - Transparent File Access (for VM). This permits a P/390 VM user to link and access a mainframe VM minidisk.

∙AWS5080 - Provides 5088-like functions using FSLA or MSLA adapters.

∙AWS2703 (dm2703) - IBM 2703 communications controller emulator, uses the Server′s serial (COM) ports to emulate asynchronous ports on an IBM 2703,

for connections (via modems) to ASCII terminal devices. (The 2703 is no longer supported by OS/390.)

∙AWSOMA - Reads a CD-ROM in OMA format. To OS/390, this appears as a 3420 or 3422 tape drive.

∙AWSPCSRV - Uses P/390 VM users to work directly with Server (OS/2 or AIX) files.

There are a considerable number of device managers; the following table may help catorgize them:

Table 1 (Page 1 of 2). Device Manager Utilization

Manager	Description	OS/390	VM	VSE	P/390	R/390
AWSCKD (dmckd)	CKD DASD	Y	NR	NR	Y	Y
AWSFBA (dasd)	FBA DASD	N	Y	Y	Y	Y
AWSC370 (dmhuron)	Bus & tag channel	Y	Y	Y	Y	Y

16 P/390 MVS

Table 1 (Page 2 of 2). Device Manager Utilization

AWSTAPE (dmtape)	pseudo tape drive	Y(1)	Y	Y	Y	Y
SCSI3480 (dm34xx)	SCSI-attached tape	Y	Y	Y	Y	Y
SCSI3420 (dm34xx)	SCSI-attached tape	Y	Y	Y	Y	Y
AWS34x0	SCSI-attached tape (2)	Y	Y	Y	Y	Y
AWS2821 (printer)	1403 printers	Y	Y	Y	Y	Y
AWS2540 (dm2540)	Emulated card reader	Y	Y	Y	Y	Y
AWS3215 (dm3215)	Typewriter console	NR(3)	Y	Y	Y	Y
AWS3274	local 3270s via CM/2	Y	Y	Y	Y	N
AWS3274 (dm3270)	local 3270s via TCP/IP	Y	Y	Y	N	Y
LAN3172 (dm3172)	SNA over LAN	Y	Y	Y	Y	Y
WAN3172	SDLC connections	Y	N	N	Y	Y
AWSICA (sdlcdm)	SDLC, BSC	N(4)	Y	Y	Y	Y
AWSPBS	BSC, SDLC	N(4)	Y	Y	Y	Y
AWSX25	X.25	N(4)	Y	Y	N	Y
LAN3274	NetBIOS and TCP/IP 3270s	Y	Y	Y	Y	N
LCS3172 (lcs3172tx,	TCP/IP on 390 OS	Y	Y	Y	Y	Y
lcs3172rx)
MGR3172	NetView	Y	N	N	Y	N
LAN3088	LAN as CTC	Y	Y	Y	Y	N
AWSTFA	VM file access	N	Y	Y	Y	N
AWS5080	5080 displays	N	Y	N	Y	N
AWS2703 (dm2703)	S/S terminals	N	Y	?	Y	?
AWSOMA	pseudo tape drive	Y(5)	Y	Y	Y	Y
AWSPCSRV	Access Server files	N	Y	N	Y	Y

Table notes: NR means not recommended. (1) AWSTAPE does not implement read backwards commands that are sometimes used by OS/390 standard label processing. (2) AWS3420 and AWS3480 are second copies of SCSI3420 and SCSI3480, permitting two drives of each type to be used. (3) AWS3215 is not recommended for the OS/390 console, but it can be useful for standalone utilities. (4) AWSICA and AWSPBS cannot be used with OS/390 VTAM; they can be used with non-VTAM BSC programs, such as JES2 NJE/RJE, although this is not formally supported. (5) The OMA format is not used for any OS/390 program distributions by IBM.

The multiple communications-oriented device managers can be confusing. The following table may help position them.

Table 2 (Page 1 of 2). Communications Device Managers

Manager	Use	OS/390	VM	VSE
AWS3274	3270s on Server display, only. For OS/390	Y	Y	Y
(P/390)	console and a few TSO and/or CICS sessions.
	Appears as local, coax-attached 3270s to
	OS/390.

Chapter 1. Product Descriptions

17

Table 2 (Page 2 of 2). Communications Device Managers

AWS3274	3270s sessions through TCP/IP (on the Server)	Y	Y	Y
(R/390)	and tn3270-type emulators. Used for the MVS
	master console, TSO, CICS, and so forth. Users
	can connect through any TCP/IP path. Appears
	as local, coax-attached 3270s to OS/390.
LAN3274	Two connection modes: NetBios and TCP/IP (on	Y	Y	Y
(P/390 only)	the server). NetBios is for OS/2 CM/2 users on
	the local LAN, and is very simple to set up.
	TCP/IP is for any tn3270-type emulator. Both
	modes appear as local, coax-attached 3270s.
LAN3172	Full LAN SNA. Appears as CTC-attached 3172.	Y	Y	Y
	Full VTAM definitions required. Can use SNA
	3270 emulators, NJE, or any other SNA LAN
	connection.
WAN3172	SDLC connections. Appears to VTAM as	Y	N	N
	CTC-attached 3172 with LAN-like connections.
	WAN3172 translates real SDLC SNA connections
	to LAN SNA connections.
AWSICA	Emulate ICA (1-2 lines). Not supported by	N	Y	Y
	OS/390 VTAM. Can be used (VM, VSE) for SDLC
	or BSC lines.
AWSPBS	Emulate ICA (more lines). Not supported by	N	Y	Y
	OS/390 VTAM. Can be used (VM, VSE) for SDLC
	or BSC lines.
LCS3172	Full TCP/IP on LAN. Appears as CTC-attached	Y	Y	Y
	3172, using two CTC addresses. Provides
	connection to OS/390 TCP/IP.
MGR3172	Connect to NetView, and associated with VTAM	Y	Y	N
(P/390 only)	resources defined for LAN3172 and WAN3172
	device managers.
AWS2703	Not supported by OS/390. Sometimes used for	N	Y	Y
	dial-in ports to VM.

1.6 Adapters and Connections

A number of optional adapters can be used with the systems. The important ones are:

∙The S/370 Channel Emulator/A adapter provides a parallel channel (ªbus and tagº) connection between Servers and mainframe control units. Only a

limited range of control units have been used with this connection. Please see 4.7.1, ªAWSC370 Device Managerº on page 106 for more detail. The same adapter is used with both P/390 and R/390 systems.

∙Token-ring and Ethernet adapters are supported for emulating an IBM 3172 Channel Station. The (emulated) 3172 can be used in a number of ways, and can provide the primary connectivity link between an OS/390 system and other systems.

∙Portmaster adapters provide up to eight SDLC (or BSC, in some cases) lines. Two of these adapters may be used.

∙Wide Area Connector (WAC) adapters are used to emulate the integrated communication adapters (ICAs) found with IBM 9221 and 9370 systems.

18 P/390 MVS

OS/390 does not generally support these devices through VTAM, but bisync (non-VTAM) can be used with these adapters. These are not used with R/390 systems. (The PS/2 Multiprotocol Adapter is no longer supported, and has been replaced by the WAC.)

∙A 4mm tape drive (standard with the system) is used (via a driver program) to emulate an IBM 3420 or 3480 tape drive.

∙A CD-ROM drive (standard with the system) is normally used for installing OS/2 programs. In principle, it should be possible to use it to hold read-only emulated 3380 disks (or read-only emulated 3420/3422 tape files), but we did not try this function. The CD-ROM can also be used through the OMA (Optical Media Attach) device manager.

∙A SCSI-attached 3480 or 3490 type tape system can be used (with the appropriate driver) as a 3480 tape system (supported by OS/390).

∙A SCSI-attached 3420 type tape system can be used (with the appropriate driver) as a 3420 tape system (supported by OS/390).

∙A number of different disk drives can be used with the systems.

1.7OS/390 on CD-ROM

IBM has available two different CD-ROM sets for OS/390. One is known as the

Preconfigured System, and the other is the Partners in Development or

Application Developers version. The difference is in the number of program products included with the systems.

OS/390, and all the auxiliary program products that are used with it, are licensed program products. You must pay the required license fees to obtain and use the products. Other things being equal, a system with more program products will have higher total license fees than a smaller system. Some program products, from IBM and other vendors, have special license fees for P/390 systems. These are often known as ESL (Entry System Level) prices. In cases where such prices do not exist, a P/390 (meaning both PC Server and RISC/6000 versions) will use the lowest tier price for the software product.

You are not required to use either of the CD-ROM OS/390 systems. However, you are required to have a proper license for any licensed software you install on your P/390 system. Note that this is a license for the software for use on the P/390. An existing license for another processor may not be acceptable, unless it is in the nature of a site license. After making the required license arrangements, you could use your existing MVS software, order new OS/390 (or MVS) software, purchase a custom-built (or express-built) OS/390 system from IBM, order the preconfigured CD-ROM, or use some other path to obtain your operating system and associated program products.

The Preconfigured System CD-ROM contains a basic OS/390 system, with no additional program products.18 It is usable, as is, but would normally be used as a base for adding additional software products. The Open Edition functions are not usable because they require RACF (an additional product) or equivalent.

18OS/390 incorporates the base MVS control program, JES2, OpenEdition, DFSMS/MVS, TCP/IP, SMP/E, TIOC, TSO/E, VTAM, LE, ISPF, HLASM, DFSMSdfp, and a number of other products. These produce a minimal, usable system. Key functions not included are RACF, SDSF, and PSF.

Chapter 1. Product Descriptions

19

IBM provides special P/390 support and terms for bona fide OS/390 (or VM or VSE) software developers. This is through the S/390 Partners in Development group (previously known as the S/390 Developers′ Association). More information is available by telephoning 1-800-627-8363 or 1-404-835-9900 (in North America), or 49-7031-16-2809 in Europe. In other locations, please ask your IBM representative for information.

A special OS/390 CD-ROM is available for members of this association. At the time this was written, the Application Developers′ CD-ROM contained the base OS/390 system, plus RACF, COBOL, C, Fortran, CICS, DB2, IMS, PSF, and a substantial list of other products.

The Preconfigured OS/390 CD-ROM has a subset of the addresses generated for the Developers′ Association CD-ROM. The full set of addresses is listed here, and all the examples in this document (and other redbooks) use these addresses. The addresses are:

S/390 Addresses	Device Type
00C	2540R
00E	1403
00F	3203-5
010	3270-X (These two 3270 devices are relics of
063	3270-X	the system used to built the CD-ROMs)
120-15F	3380
240-25F	3380	(Reduced from 200-25F range)
260-27F	3390	(Added for OS/390 AD CD-ROM)
560-57F	3480
580-5AF	3400	(Range extended to 5AF)
5A0-5AF	3422
700	3270	(OS/390 console)
700-73F	3277
900-91F	3277
A80-ABF	3390
E20-E27	CTC
E40-E47	CTC

After installing OS/390 from the CD-ROMs, you can change or add to these addresses by using HCD in the normal manner.

1.8 Positioning and Usage

Experienced MVS customers will naturally compare P/390 and R/390 systems with their mainframes. While the P/390-based systems use ªrealº mainframe software, OS/390 and a large variety of subsystems and applications, they should not be considered mainframes. Some differences are:

∙IBM mainframes have many layers of (hardware) recovery functions, some of which (in newer systems) are very sophisticated. Major mainframes have multiple processors, and transparent recovery mechanisms operate across the complete complex.

∙The Servers uses small-system disks (and the P/390 support programs do the necessary functions to emulate mainframe disks).

∙Mainframe channels and control units use intricate webs of multiple paths to devices, and devices shared with multiple processors. In later mainframes, this all takes place at a level below the operating system. This sharing of devices has become a fundamental design element of production installations.

20 P/390 MVS