IBM ZVM - FOR LINUX V6 RELEASE 1 User manual

z/VM
Getting Started with Linux on System z
version6release1
SC24-6194-00


z/VM
Getting Started with Linux on System z
version6release1
SC24-6194-00


Note:
Before using this information and the product it supports, read the information under “Notices” on page 143.
This edition applies to version 6, release 1, modification 0 of IBM z/VM, (product number 5741-A07) and to all
subsequent releases and modifications until otherwise indicated in new editions.
This edition replaces SC24-6096-03.
© Copyright International Business Machines Corporation 2009.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.

Contents
About this document .........v
Intended audience ............v
Conventions and terminology used in this document v
Where to find more information .......vi
Additional Publications .........vi
How to send your comments to IBM . . ix
If you have a technical problem........ix
Summary of changes.........xi
SC24-6194-00, z/VM Version 6 Release 1 .....xi
Chapter 1. About z/VM ........1
Overview of the Control Program (CP) .....3
Central processing units (CPUs) .......3
Storage ...............3
DASD and minidisks ..........4
Temporary minidisks ..........4
Virtual disks in storage ..........4
Virtual readers, punches, and printers .....4
The virtual machine console ........4
Overview of the CP spool file system .....7
The user directory ...........8
Overview of the Conversational Monitor System
(CMS) ................9
Minidisks and the CMS access mode .....9
CMS files ..............11
The PROFILE EXEC ..........12
The Help system ...........13
The CMS file editor XEDIT .........15
Input mode .............17
Overview of changing files ........18
SAVE, FILE, QUIT, and QQUIT.......19
Summary of Linux and z/VM similarities ....20
Chapter 2. Planning for Linux virtual
servers ..............21
Overview of z/VM capacity planning .....22
Estimating memory and CPU requirements....25
Overview of estimating memory and CPU
requirements .............25
Steps for estimating memory and CPU
requirements .............27
Guidelines for estimating the amount of DASD you
need.................28
For z/VM paging ...........28
For the Linux file system .........29
Planning your network ..........30
TCP/IP networking options for Linux ....30
Giving Linux virtual servers access to
cryptographic hardware for SSL acceleration . . 31
Planning for user management ........32
Steps for obtaining documentation and media . . . 34
Chapter 3. Changing the system
configuration ............35
Overview of the SYSTEM CONFIG file .....35
Steps for adding a paging, spooling, or user volume 35
Steps for releasing the primary parm disk ....37
Steps for updating the CP-owned volume list . . . 37
Steps for updating the default system identifier . . 39
Steps for updating the user volume list .....40
Steps for setting up warm start, clearing tdisk space,
and other features ............41
Steps for controlling access to devices at startup . . 43
Steps for defining a virtual switch .......44
Steps for setting addresses for consoles .....46
Steps for updating special escape character defaults 47
Steps for checking the syntax of the SYSTEM
CONFIG file ..............48
Steps for restoring CP’s access to the primary parm
disk .................49
Chapter 4. Configuring the Directory
Maintenance Facility .........51
Steps for enabling DirMaint .........51
Steps for changing the passwords for DirMaint
service machines ............52
Steps for configuring DirMaint ........53
Steps for authorizing users to perform DirMaint
tasks.................54
Steps for controlling where DirMaint creates
minidisks ...............55
Steps for copying the current USER DIRECT file . . 57
Steps for putting the configuration into production
and starting DirMaint ...........58
Steps for automatically starting DIRMAINT . . . 59
Steps for testing DirMaint .........60
Step for modifying the OPERATOR’s directory entry 60
Chapter 5. Configuring TCP/IP ....63
Setting up the production TCP/IP .......63
Steps for automatically starting TCP/IP .....63
Chapter 6. Restarting z/VM and
checking the system.........67
Steps for restarting z/VM .........67
Steps for checking paging and spooling space . . . 67
Step for checking the system identifier .....68
Step for checking the user volume list .....68
Steps for checking features .........69
Step for checking offline devices .......69
Step for checking the virtual switch ......69
Step for checking character defaults ......70
Steps for checking TCP/IP .........70
Chapter 7. Creating your first Linux
virtual machine and installing Linux . . 71
© Copyright IBM Corp. 2009 iii

Overview of defining virtual machines for Linux . . 71
Steps for defining a master virtual machine for
Linux ................71
Steps for setting up LINMSTR’s disks .....75
Installing Linux in a virtual machine ......77
Overview of installing Linux in a virtual machine 77
Example of using FTP to get the Linux boot files 79
Example of punching Linux boot files to the
virtual machine reader..........80
Example of booting (IPL) the Linux boot files
from the virtual machine reader ......81
(Optional) Steps for loading Linux automatically at
logon ................82
Chapter 8. Cloning Linux virtual
servers ..............83
Steps for cloning a Linux virtual server .....83
Chapter 9. Setting up basic system
automation .............85
Starting and stopping virtual machines
automatically ..............85
Steps for automatically starting Linux virtual
servers and other virtual machines .....85
Steps for enabling Linux virtual servers to shut
down automatically ..........87
Setting up the programmable operator .....88
Overview of the programmable operator . . . 88
Steps for setting up the routing table .....89
Steps for setting up the programmable operator 92
Steps for automating Linux virtual consoles . . 93
Steps for testing your automation ......95
Chapter 10. Performing run-time tasks 97
Overview of console types .........97
Real operation tasks ...........98
Step for monitoring the logical operator console 98
Step for restarting z/VM ........100
Step for managing real devices ......100
Step for managing users.........105
Virtual machine operation tasks .......107
Steps for using CP commands at the Linux
virtual console ............108
Archiving and backing up critical data .....112
Overview of archiving z/VM system data . . . 112
Archiving virtual server disks .......113
Chapter 11. Monitoring performance
and capacity ............117
Overview of performance monitoring .....117
Monitoring Linux virtual servers with
Performance Toolkit for VM .......118
Overview of the z/VM scheduler......118
Steps for taking a snapshot of system performance 120
Using the CP Monitor and Performance Toolkit for
VM.................123
Overview of the CP Monitor and Performance
Toolkit for VM ............123
Configuring Performance Toolkit for VM . . . 124
Using monitoring to analyze performance and
capacity ..............133
Steps for using CP commands to improve
performance..............135
Chapter 12. Servicing z/VM .....137
z/VM service concepts ..........137
Appendix. Example of using FTP to
install Linux from the hardware
management console ........139
Linking the HMC removable media to your z/VM
logical partition ............139
FTPing to the HMC removable media .....140
Notices ..............143
Trademarks ..............145
Glossary .............147
Bibliography............149
Where to Get z/VM Information .......149
z/VM Base Library ...........149
Overview..............149
Installation, Migration, and Service .....149
Planning and Administration .......149
Customization and Tuning ........149
Operation and Use ..........149
Application Programming ........149
Diagnosis..............150
z/VM Facilities and Features ........150
Data Facility Storage Management Subsystem
forVM..............150
Directory Maintenance Facility for z/VM . . . 150
Open Systems Adapter/Support Facility . . . 150
Performance Toolkit for VM .......151
RACF Security Server for z/VM ......151
Remote Spooling Communications Subsystem
Networking for z/VM .........151
Prerequisite Products ...........151
Device Support Facilities ........151
Environmental Record Editing and Printing
Program ..............151
Additional Publications ..........151
Index ...............153
iv z/VM: Getting Started with Linux on System z

About this document
This document describes how to configure and use z/VM®functions and facilities
for Linux®servers running on the IBM®System z®platform (hereafter referred to
as the mainframe). The document provides requirements and guidelines to
implement during z/VM installation, but primarily assumes you have installed
z/VM and are ready to deploy Linux in virtual machines.
Early sections acquaint you with z/VM and take you from the point after z/VM
installation to the point where you are ready to install your first Linux server. At
that point you must turn to the installation documentation provided by your Linux
distributor. Following the deployment of your first Linux server, you can replicate
or clone additional servers.
When you finish the early sections, you will have two or more Linux servers
running on z/VM with TCP/IP connections to the network. Subsequently, you can
turn to vendor-supplied documentation to install applications on Linux. Later
sections cover operations, administration, performance, and other day-to-day bare
essentials.
Intended audience
This document is designed to help anyone who does system programming,
administration, or operation, but has limited knowledge of z/VM and wants to get
started deploying Linux servers on z/VM. Before you begin, you must:
vUnderstand mainframe hardware concepts, such as logical partitions (LPARs)
and I/O
vKnow and have used the Linux operating system
vKnow and have used TCP/IP.
The environment for your z/VM system environment is assumed to include:
vA mainframe with an OSA-Express device
vz/VM version 6 release 1
vDirectory Maintenance Facility
vPerformance Toolkit for VM
vIf you do not have an external file server for the Linux code, you might need an
NFS or FTP server.
Conventions and terminology used in this document
This document is primarily a cookbook; that is, it provides instructions about how
to accomplish a task or goal. When required, background concepts are provided to
help you understand a key z/VM function or facility. Instructions and background
concepts are separated but linked together through cross-references, providing an
efficient path through the instructional material. At the beginning of each set of
instructions, you will see a Before you begin section, which explains what you
need to know or to do before you perform the task. Cross-references in the Before
you begin section take you to the necessary background concepts. Thus, if you
already know the necessary concepts, you do not need to read those background
topics and can simply follow the instructions.
© Copyright IBM Corp. 2009 v

Though the topics in this document are self-sufficient, you might want to explore a
function or facility in detail. Some topics end with a list of documents that you can
use to understand a function or facility in detail.
In general, new terms (in italics) are defined in the context they are introduced.
Sometimes the manual focuses on the virtual machine functions (the virtual
hardware) and other times the complete Linux server system (the virtual machine
and the Linux operating system as a whole). When focusing on the virtual machine
functions only, the term virtual machine or virtual machine for Linux is used. The
term Linux virtual server refers to the complete Linux system (virtual machine
hardware and the Linux operating system as a whole) running on z/VM.
Commands and statements that you must type are in bold while system responses
are in normal font.
Example: In the example, you would type “query processors”. The rest of the
example is the system response:
query processors
PROCESSOR 00 MASTER
PROCESSOR 01 ALTERNATIVE
Ready;
Variable information appears in bold italics, which means you must substitute
your own values for the variable.
Example: For the command, you would need to supply your own password for
the variable new_password.
dirm add linmstr like linux pw new_password
A vertical ellipsis
.
.
.
indicates system responses that have been removed for clarity.
Where to find more information
For z/VM terms used in this document, see z/VM: Glossary or use the z/VM HELP
Facility (for more information about glossary terms and the z/VM HELP Facility,
see “Glossary” on page 147).
For more information about related publications, see “Bibliography” on page 149.
Additional Publications
For white papers, IBM Redbooks®publications, and other useful information about
Linux on the mainframe, visit the z/VM resources for Linux on IBM System z Web
site at:
http://www.vm.ibm.com/linux/
Publications you might be interested in are:
vi z/VM: Getting Started with Linux on System z

vz/VM and Linux on IBM System z: The Virtualization Cookbook for SLES9, SG24-6695
vSecurity on z/VM, SG24-7471
Links to Other Online Documents
If you are viewing the Adobe®Portable Document Format (PDF) version of
this document, it might contain links to other documents. A link to another
document is based on the name of the requested PDF file. The name of the
PDF file for an IBM document is unique and identifies the edition. The links
provided in this document are for the editions (PDF names) that were current
when the PDF file for this document was generated. However, newer editions
of some documents (with different PDF names) might exist. A link from this
document to another document works only when both documents reside in
the same directory.
About this document vii

viii z/VM: Getting Started with Linux on System z

How to send your comments to IBM
We appreciate your input on this publication. Feel free to comment on the clarity,
accuracy, and completeness of the information or give us any other feedback that
you might have.
Use one of the following methods to send us your comments:
1. Send an e-mail to [email protected]
2. Visit the z/VM reader's comments Web page at www.ibm.com/systems/z/os/
zvm/zvmforms/webqs.html
3. Mail the comments to the following address:
IBM Corporation
Attention: MHVRCFS Reader Comments
Department H6MA, Mail Station P181
2455 South Road
Poughkeepsie, NY 12601-5400
U.S.A.
4. Fax the comments to us as follows:
From the United States and Canada: 1+845+432-9405
From all other countries: Your international access code +1+845+432-9405
Include the following information:
vYour name and address
vYour e-mail address
vYour telephone or fax number
vThe publication title and order number:
z/VM V6R1 Getting Started with Linux on System z
SC24-6194-00
vThe topic and page number related to your comment
vThe text of your comment
When you send comments to IBM, you grant IBM a nonexclusive right to use or
distribute your comments in any way it believes appropriate without incurring any
obligation to you.
IBM or any other organizations will only use the personal information that you
supply to contact you about the issues that you submit to IBM.
If you have a technical problem
Do not use the feedback methods listed above. Instead, do one of the following:
vContact your IBM service representative.
vContact IBM technical support.
vVisit the z/VM support Web page at www.vm.ibm.com/service/
vVisit the IBM mainframes support Web page at www.ibm.com/systems/
support/z/
© Copyright IBM Corp. 2009 ix

xz/VM: Getting Started with Linux on System z

Summary of changes
This document contains terminology, maintenance, and editorial changes. Technical
changes or additions to the text and illustrations are indicated by a vertical line to
the left of the changes. Some program updates might be provided through z/VM
service by program temporary fixes (PTFs) for authorized program analysis reports
(APARs), which also might be available for some prior releases.
SC24-6194-00, z/VM Version 6 Release 1
This edition supports the general availability of z/VM V6.1. Changes made are:
vA step was added to “Steps for copying the current USER DIRECT file” on page
57.
vOther minor technical and editorial changes.
© Copyright IBM Corp. 2009 xi

xii z/VM: Getting Started with Linux on System z

Chapter 1. About z/VM
This topic is a z/VM primer and covers general VM concepts, such as editing and
finding files, required to complete z/VM system tasks.
When you log onto z/VM, you have the functional equivalent of a real computer
and its associated devices at your fingertips. This functional equivalent of a
computing system is called a virtual machine. Virtual machines are not real, but do
work like real systems. Everyone in your entire organization can use z/VM to
share the resources of a single computer, while at the same time accessing the
system as if each is the only user.
Figure 1 shows a stylized representation of a real mainframe computing system.
Each real computing system has one or more central processing units (CPUs),
storage (memory), peripheral devices for input and output, such as disks, tapes,
printers, and displays, and the operator console. The operating system manages all
these resources to do work.
z/VM virtualizes real computing resources so that each user appears to have a
complete mainframe computing system, as shown in Figure 2 on page 2. This
means each virtual machine can run its own operating system to manage its virtual
resources. It also means you can perform virtual machine tasks as if they were real
machine tasks: you can boot (perform an initial program load of) an operating
system, attach and detach devices, and manage the work of your virtual machine
operating system.
CPU
1
.
.
.
CPU
2
CPU
n
CPU
0
central storage
channels
control
units
operating system
disk tape printer
operator
console
user
displays
Figure 1. Representation of a mainframe computing system
© Copyright IBM Corp. 2009 1

A virtual machine is directly associated with a z/VM user ID or logon identifier.
When you log onto z/VM, you have a virtual machine at your disposal and
control the virtual machine the way a system operator controls the real hardware.
Some user IDs (virtual machines) are given special privileges to control z/VM and
the real machine. For example, the OPERATOR has special privileges allowing
control of real machine resources. Another user, usually called MAINT, has special
privileges to change z/VM code, apply z/VM maintenance, and add new users.
Whether or not users have special privileges, they all perform their tasks through a
virtual machine. So, as shown in Figure 2, some virtual machines run Linux, while
others run other operating systems, such as the Conversational Monitor System
(CMS) (more about CMS in a moment).
The Control Program (CP) is the component of z/VM that manages the resources
of a single computer so that multiple computing systems (virtual machines) appear
to exist. Think of CP as a supervisor (or hypervisor) program running in a layer
between the hardware and virtual machines. When you are working in the CP
environment, you are provided with CPU (central processing unit) functions, input
and output devices, and storage. Through CP, each virtual machine can run its
own operating system, such as Linux, z/OS®, or z/VM itself.
Operating systems running in virtual machines are often called guests. Other terms
and phrases you might encounter are:
.
.
.
.
.
.
.
.
.
.
.
.
channels
.
.
.
control
units
disk printer
z/VM operator
console
z/VM
Linux
Linux
.
.
.
Linux (other)
Linux CMS
tape
.
.
.
CPU
1
CPU
2
CPU
n
CPU
0
Figure 2. Representation of virtual machines
2z/VM: Getting Started with Linux on System z

vRunning first level: running directly on the hardware, which is what z/VM does.
vRunning second level or running under VM or running on (top of) VM: running as a
guest.
During its time slice, a guest actually runs on the real machine. The hardware
microcode handles most guest program instructions and CP takes control only
when necessary, which maintains good performance.
The Conversational Monitor System (CMS) is the interactive component of z/VM.
CMS is a single-user operating system that runs in a virtual machine. Typically,
each directory entry (user definition) has a statement that loads the CMS operating
system at logon time (see “The user directory” on page 8). CMS is not only an
end-user interactive component, but a home for running system utilities and tasks,
such as TCP/IP and system management functions. At the z/VM level, systems
personnel use CMS to manage z/VM itself and guests. At the guest level, you can
use CMS to define resources for your virtual machine, so loading CMS is useful
even if you plan subsequently to load Linux into the same virtual machine.
Overview of the Control Program (CP)
CP acts as a hypervisor layer between the hardware and virtual machines. Each
virtual machine appears to have its own CPU, storage (memory), and devices. In
reality, these items can be
vReal. For example, you can dedicate a real network interface to a virtual
machine for its exclusive use.
vShared. For example, the CPU is shared through time sharing and real storage is
shared as virtual storage. What appears as real storage to a guest is actually
virtual storage to CP.
vSimulated. For example, a virtual switch is a simulated LAN networking switch.
CP transparently maps virtual devices and resources to their real counterparts.
Topics in this section explain how CP manages computer resources for virtual
machines.
Central processing units (CPUs)
A virtual machine can have up to 64 virtual CPUs. If capable of running in
multiprocessor mode, your virtual machine operating system dispatches work on
its virtual CPUs as if it were running on real hardware. CP handles the dispatching
of work on your virtual CPUs to real CPUs.
Guideline: Never give a virtual machine more virtual CPUs than there are real
CPUs.
Usually virtual machines share all CPUs, but a real CPU can be dedicated to a
virtual machine, which means that the CPU is reserved for that virtual machine’s
exclusive use. This obviously has an impact on the performance of other virtual
machines in the system.
Storage
Mainframe storage is analogous to memory in a personal computer. CP commands
refer to memory as storage, so do not confuse the term “storage” with disk or tape
storage.
Chapter 1. About z/VM 3

Each virtual machine has its own virtual storage. CP manages the residency of
virtual machine’s pages in real storage through paging. Pages that have not been
referenced can be moved out of real storage into either expanded storage or onto a
paging device. When a virtual machine requires a page no longer in real storage, a
page fault occurs and CP brings the missing page back into real storage.
CP has facilities that allow portions of real storage to be shared by many virtual
machines. Such portions are called shared segments. This sharing economizes on real
storage and requires less paging, thereby improving performance. For example, the
CMS nucleus is shared in real storage by all virtual machines that loaded CMS by
name; that is, every CMS virtual machine mapsa1MBsegment of virtual storage
to the same 1 MB of real storage.
DASD and minidisks
DASD, the mainframe term for disk drives, stands for “direct access storage
device” and is analogous to a hard disk drive on a personal computer. A single
real DASD is called a volume or real volume. Each volume has a label or volume serial
number (volser) that identifies the volume to z/VM.
Of special importance is the way z/VM shares DASD. CP can logically partition
real DASD volumes into minidisks, which is analogous to dividing a personal
computer hard disk into multiple partitions. A minidisk has its own label, which is
distinct from the real DASD label. Each virtual machine can have one or more
minidisks and those minidisks are under control of the guest operating system. To
the guest, a minidisk appears as an entire DASD volume (though smaller) and the
guest runs channel programs as normal to do I/O. Behind the scenes, CP reorients
the channel programs: the guest perceives all minidisks as starting at cylinder 0,
but the real DASD volume has only one cylinder 0, so CP must modify the
cylinder offsets in the channel program to address DASD cylinders owned by the
guest.
Temporary minidisks
You can create a temporary minidisk from a special pool of real disks. The disk
lasts as long as the virtual machine is logged on. At logoff, the temporary minidisk
is deleted and the space returned to the available temporary disk pool.
Virtual disks in storage
Virtual disks in storage are similar to temporary minidisks, except the disks are
mapped to storage rather than the cylinders of real disks. Using virtual disks in
storage avoids the need for disk I/O. CP manages the virtual disk pages as part of
its real memory management.
Virtual readers, punches, and printers
These devices are not associated with real devices, but are implemented through
the spool file system. For more information, see “Overview of the CP spool file
system” on page 7.
The virtual machine console
The virtual machine console or virtual console is the primary interface to the virtual
machine. When you log on to a virtual machine from a local terminal or a remote
workstation, the virtual console is associated with the terminal session. From the
4z/VM: Getting Started with Linux on System z

console, you can enter CP commands, such as loading (IPL) an operating system.
The virtual console is the device an operating system views as its system or
hardware console.
Note: The key assignments for your keyboard might differ from standard key
assignments. Some 3270 emulators allow you to remap the key assignments;
for example, the Clear function might be assigned to the ESC key on some
keyboards and the Pause/Break key on others. Consult your display
documentation for key mappings.
As you do work on your console, the lower right corner of the screen displays
various status notices. The notices tell you what is happening in the system at the
present time. If you forget what these notices mean, you can come back to this
section for reference.
CP READ
This notice means that the Control Program (CP) is waiting for you to
enter a command.
VM READ
This notice means that a virtual machine operating system, such as CMS, is
waiting for you to enter a command.
RUNNING
This notice means the virtual machine is working on something. For CMS,
this means CMS is ready for you to enter a command.
MORE ...
This notice means that there is more information than can fit on the
current screen. After a pause (which depends on the terminal settings for
your virtual machine), the next screen of information is displayed. To view
the next screen right away, press the Clear key. To hold this information on
the screen, press the Enter key, which changes MORE... to HOLDING.
HOLDING
This notice means the system is waiting for you to clear the screen before
showing you more information. The notice appears when the screen
displays MORE... and you press the Enter key. The notice can also appear
when another user sends you a message. To cancel the hold, press the
Clear key.
NOT ACCEPTED
This notice means that the system is working on something and is too
busy to accept another command. Wait several seconds and issue your
command again.
Related information
For more information about virtual consoles, see “Using a Virtual Machine
Operator’s Console” in z/VM: Virtual Machine Operation.
CP commands
CP provides you with commands that allow you to view and manipulate your
virtual hardware (virtual CPUs, virtual storage, minidisks, and other devices). To
issue some CP commands, you need to be in a special privilege class assigned to
you in the user directory. Privilege classes are denoted by the letters A through Z,
the numbers 1 through 6, or the word ″Any.″For the tasks explained in this
document, the user IDs you use have all the required privilege classes (like
superusers in Linux).
Chapter 1. About z/VM 5

Related information
For more information about privilege classes, see “Privilege Classes” in z/VM: CP
Commands and Utilities Reference.
Examples of using the CP commands: QUERY displays information about your
virtual machine.
1. To display virtual CPUs, class G users can issue the QUERY VIRTUAL CPUS
command:
query virtual cpus
CPU 00 ID FF05152120640000 (BASE)
Ready;
The response tells you the virtual machine has one base virtual CPU whose
address is 00.
2. To display available storage (memory), class G users can issue the QUERY
STORAGE command:
query virtual storage
STORAGE = 512M
Ready;
The response tells you the virtual machine has 512 megabytes of storage.
3. To display information about minidisks, class G users can issue the QUERY
VIRTUAL DASD command:
query virtual dasd
DASD 0120 3390 PK5001 R/O 250 CYL ON DASD 810B SUBCHANNEL = 000D
DASD 0190 3390 SYGEMC R/O 130 CYL ON DASD 7355 SUBCHANNEL = 0005
DASD 0191 3390 USGE24 R/W 10 CYL ON DASD 7378 SUBCHANNEL = 0000
DASD 019A 3390 PK5001 R/O 400 CYL ON DASD 810B SUBCHANNEL = 0009
DASD 019D 3390 US7E0K R/O 250 CYL ON DASD 801C SUBCHANNEL = 0006
The response tells you the virtual machine has 5 minidisks, one of which is
read/write (R/W); the others are read only (R/O).
4. To display information about network devices such as the Open Systems
Adapter, class G users can issue the QUERY VIRTUAL OSA command:
query virtual osa
OSA F5F0 ON OSA F599 SUBCHANNEL = 0000
F5F0 DEVTYPE OSA CHPID 76 OSD
F5F0 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE
OSA F5F1 ON OSA F59A SUBCHANNEL = 0001
F5F1 DEVTYPE OSA CHPID 76 OSD
F5F1 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE
OSA F5F2 ON OSA F59B SUBCHANNEL = 0002
F5F2 DEVTYPE OSA CHPID 76 OSD
F5F2 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE
5. To display the size of real storage, class B and E users can issue the QUERY
STORAGE command:
query storage
STORAGE = 512M
Note: QUERY VIRTUAL option displays information about the virtual machine.
The keyword “VIRTUAL” is optional for the class G user. For privileged
6z/VM: Getting Started with Linux on System z