Reference, cheat sheets, blank worksheets, and education
This appendix provides extra materials that are included for your reference. These materials can be printed or downloaded, as described. In addition, links to where you can obtain self-learning educational information are included.
This appendix includes the following topics:
Related books and publications
The following publications can be used as information sources:
•z/VM installation guide
You want to have a copy of z/VM 7.2.0 Installation Guide, GC24-6292, to use as reference.
•z/VM Internet Library
Online documentation is at this web page.
The following useful publications are available at this web page:
– z/VM CP Messages and Codes
– z/VM TCP/IP Messages and Codes
– z/VM CP Commands and Utilities Reference
– z/VM CP Planning and Administration
– z/VM Getting Started with Linux on System z
– z/VM TCP/IP Planning and Customization
– z/VM Performance Toolkit Guide, SC24-6156
– z/VM Performance Toolkit Reference, SC24-6157
•z/VM configuration and performance information from Dr. Brian Wade:
The authoritative source of detailed information for the how and why IBM Z and LinuxONE systems work; often referred to as The Z POp.
•IBM DeveloperWorks guides
•Linux390 reference documentation on IBM DeveloperWorks
The following documents are available at this web page:
– Kernel Messages (Kernel 4.19), SC34-2599
– Pervasive Encryption for Data Volumes, SC34-2782
– Getting Started with Pervasive Disk Encryption, SC34-2783
– libica Programmer’s Reference, SC34-2602
– Secure Key Solution with the Common Cryptographic Architecture Application Programmer's Guide, SC33-8294
– Exploiting Enterprise PKCS #11 using openCryptoki, SC34-2713
•Linux distribution-specific materials: SUSE Linux Enterprise Server 12 on IBM z Systems
•IBM Redbooks publications
The following IBM Redbooks publications are available at this web page:
– IBM z Systems Connectivity Handbook, SG24-5444
– Deploying a Cloud on IBM System z, REDP-4711
– Installing Oracle 11gR2 RAC on Linux on System z, REDP-4788
– Linux on IBM System z: Performance Measurement and Tuning, SG24-6926
– Fibre Channel Protocol for Linux and z/VM on IBM System z, SG24-7266
– Security for Linux on System z, SG24-7728
– Advanced Networking Concepts Applied Using Linux on IBM System z, SG24-7995
– Set up Linux on IBM System z for Production, SG24-8137
– Practical Migration from x86 to Linux on IBM System z, SG24-8217
– End-to-End High Availability Solution for System z from a Linux Perspective, SG24-8233
– Security for Linux on System z: Securing Your Network, TIPS0981
– Linux on System z: An Ideal Platform to Migrate Your IT Workload, TIPS1166
– Linux on IBM eServer™ zSeries and S/390®: Performance Toolkit for VM, SG24-6059
– Printing with Linux on zSeries Using CUPS and Samba, REDP-3864
Online resources
The following websites and URLs are also relevant as further information sources:
•The z/VM customer presentation library page:
•The Linux for z Systems and S/390 portal:
•The IBMVM list server:
•The linux-390 list server:
•Red Hat Enterprise Linux Server no-charge evaluation download for IBM z Systems:
•SUSE Linux Enterprise Server no-charge evaluation download for IBM z Systems:
•z/VM publications:
•z/VM performance tips:
•z/VM VDISK for Linux swap performance tips:
•z/VM TCP/IP planning, customization, and reference:
•z/VM TCP/IP cryptographic security:
•z/VM user’s guides and command references (XEDIT, Conversational Monitor System (CMS), and others):
•XEDIT for VM/SP System Product R3 (historical reference):
•Rex Swain’s XEDIT summary page
•Debian Linux S/390 port:
Important z/VM files
z/VM differs from Linux in the location and number of configuration files. In Linux, many configuration files exist and most of them are in or under the /etc/ directory. On z/VM, relatively few configuration files exist. However, they are on many different minidisks. Table B-1 on page 478 provides a summary and the location of important z/VM configuration files.
Table B-1 Important z/VM configuration files
|
File
|
Location
|
Description
|
|
SYSTEM CONFIG
|
PMAINT CF0
|
This file is the operating system’s main configuration file. It defines the system name, control program (CP) volumes, user volumes, and other settings.
|
|
USER DIRECT
|
MAINT 2CC
|
This file is the initial z/VM user directory. All virtual machines that are known to the system are defined here. If a directory maintenance product is in use, this file is no longer authoritative.
|
|
PROFILE TCPIP
|
TCPMAINT 198
|
This file defines the resources for the primary z/VM TCP/IP stack, including the TCP/IP address, Open Systems Adapter (OSA) resources, subnet mask, and gateway. It is initially created by the IPWIZARD tool as PROFILE TCPIP.
|
|
SYSTEM DTCPARMS
|
TCPMAINT 198
|
This file is created to define the TCP/IP stacks on the system. It is initially created by the IPWIZARD tool.
|
|
TCPIP DATA
|
TCPMAINT 592
|
This file defines the Domain Name System (DNS) server, the domain name, and other settings. It is initially created by the IPWIZARD tool.
|
|
PROFILE EXEC
|
AUTOLOG1 191
|
This file is a REXX EXEC that is run when the system starts. It is analogous to the /etc/inittab file in Linux.
|
Cheat sheets
This section contains quick references or “cheat sheets” for the XEDIT and vi editors.
XEDIT cheat sheet
XEDIT has line commands that are typed on the command line (====>) and prefix commands, which are typed over the line numbers on the left side of the window.
Line commands
Do not include the angle brackets (< >) in your commands:
a Add a line.
a<n> Add <n> lines.
c/<old>/<new>/<n> <m>
Search for string <old> and replace it with <new> for <n> lines below the current line and <m> times on each line. An asterisk (*) can be used for <n> and <m>.
/<string> Search for ‘string’ from the current line.
-/<string> Search backwards for ‘string’.
all /<string>/ Show all occurrences of ‘string’ and hide other lines.
bottom Move to the bottom of the file.
top Move to the top of the file.
down <n> Move down ‘n’ lines.
up <n> Move up ‘n’ lines.
file Save the current file and exit XEDIT.
ffile Save the current file and exit but do not warn of overwrite.
save Save the current file but do not exit.
quit Exit XEDIT if no changes were made.
qquit Exit XEIDT even if changes were not saved.
left <n> Shift ‘n’ characters to the left.
right <n> Shift ‘n’ characters to the right.
get <file> Copy file and insert past the current line.
input Enable INPUT mode to insert multiple lines of text, beginning at the current line.
:<n> Move to line ‘n’.
? Display the last command.
= Execute the last command.
x <file> Edit ‘file’ and put it into the XEDIT “ring”.
x Move to the next file in the ring.
Prefix commands
Prefix commands are typed over the line numbers on the left side of the window:
a Add one line.
a<n> Add 'n' lines.
c Copy one line.
cc Copy a block of lines.
d Delete one line.
dd Delete a block of lines.
f Line after which a copy (c) or a move (m) is to be inserted.
p Line before which a copy (c) or a move (m) is to be inserted.
i Insert a line.
i<n> Insert 'n' lines.
m Move one line.
mm Move a block of lines.
" Replicate a line.
"<n> Replicate a line 'n' times.
"" Replicate a block of lines.
You may also want to refer to “Online resources” on page 477, for a more expansive XEDIT summary option.
A vi cheat sheet
The following list is a small subset of vi commands that are most commonly used. The vi editor has three modes:
•Input mode: The Insert key, i, o (add a line below), O (add a line above), and other commands put you in this mode where you can type text into the file. When you are in this mode, you see the text --INSERT-- in the last line.
•Command mode: The Esc key takes you out of input mode and into command mode. You can issue the following commands:
i Brings you back to input mode.
dd Deletes a line and puts it in the buffer.
<n>dd Delete <n> lines.
x Delete a character.
dw Delete a word.
p Add the buffer past the current location.
P Add the buffer before the current location.
o Add a line and go into insert mode.
/string Search for string.
n Execute the last command again (This function can be powerful).
jkl; Cursor movement.
A Add text at the end of the line.
<nn>G Go to line <nn>.
G Go to the last line in the file.
yy Yank a line (copy into buffer).
<n>yy Yank n lines.
•Command-line mode: Pressing the colon (:) key brings you to this mode at the bottom of the window. You can issue the following commands:
:wq Save (write and quit).
:q! Quit and discard changes.
:<nn> Go to line number <nn>.
:r <file> Read <file> into the current file.
:1,$s/old/new/g Globally replace <old> with <new>.
:help Give help.
DirMaint cheat sheet
The following list shows useful DirMaint commands:
Add Add a user or profile directory entry.
AMDisk Add a minidisk.
DEDicate Add or delete an existing dedicate statements.
DMDisk Remove a minidisk.
FILE Add or replace a DirMaint control file.
RLDCode Reload the DirMaint resident operating procedures.
RLDExtn Reload the DirMaint CONFIG* DATADVH file.
REView Review a user or profile directory entry.
MDisk Change the access mode and passwords for minidisks.
STorage Change the logon storage size.
SEND Request a copy of a DirMaint control file.
SETOptn Add, change, or delete CP options.
CLAss Change the CP class for a directory entry.
SPEcial Add or delete an existing special statement.
DirMaint example commands
The following examples show DirMaint commands:
•Add a new 50 cylinder minidisk 200 to user ID spiedie:
DIRMAINT FOR SPIEDIE AMDISK 0200 3390 AUTOG 00050 {VOLUMEGROUP}
•Add a link statement to the TCPMAINT 592 minidisk into the directory entry for user vmfrau:
DIRMAINT FOR VMFRAU LINK TCPMAINT 0592 0592 RR
Editing a full profile record from DirMaint
DIRMAINT FOR SOMEUSER GET LOCK
RECEIVE 0234 = = A
XEDIT SOMEUSER DIRECT A
DIRMAINT FOR SOMEUSER REPLACE
|
Important: Consider the following points:
•While you are editing a directory entry that you received by using the DIRMAINT FOR ... GET command, the last line of the file contains internal data that is used by DirMaint during processing.
Do not change, delete, or move the line beginning with *DVHOPT.
•If you accidentally delete or modify the *DVHOPT line, use the XEDIT subcommand QQUIT to quit without saving your changes, then restart your XEDIT session for the file. This approach will work if you did not use the SAVE subcommand during your XEDIT session.
If you performed an intermediate SAVE, use QQUIT to exit without saving any further changes, ERASE the locally saved directory entry from your A disk, unlock the record by issuing the command DIRMAINT FOR ... UNLOCK, and then start over again.
|
Blank planning worksheet
This section contains a blank copy of the planning worksheet that is used in section 2.1.2, “IBM Dynamic Partition Manager” on page 35. This worksheet is included for your convenience. Hopefully, it is organized in the order that you will need the data. It is recommended that you specify all of the applicable values in the worksheet to simplify and expedite your installation process.
|
Tip:
Print out these pages that comprise the planning worksheet so you can physically write on them to complete each section. We recommend that you use simplex mode (printing only on one side of each piece of paper). You will have an easier time completing the sheets when you do not have to flip back and forth as much. In addition, if you choose to then scan your completed sheets for reference/archive purposes, this can greatly simplify that task as well.
|
IBM Shop Z
If you are ordering z/VM by using Shop Z, as described in section 5.1, “Obtaining z/VM through electronic download” on page 98, use Table B-2 to record the values that you will use.
Shop Z home page: http://www.ibm.com/software/shopzseries
Table B-2 Shop Z data
|
Name
|
Value
|
|
User ID
|
|
|
Order number
|
|
|
Order name
|
|
|
Date/Time
|
|
Hardware Management Console
In Chapter 5.3, “Installing z/VM from a DVD or an FTP server” on page 110, we describe how to start a z/VM installation from the Hardware Management Console (HMC). Complete Table B-3 to record the values that you will use.
Table B-3 HMC values
|
Name
|
Value
|
|
HMC location or URL
|
|
|
HMC user ID
|
|
|
FTP source system
(if installing from FTP)
|
|
|
z/VM installation directory
|
|
z/VM Installation Planning Panels (INSTPLAN)
In Chapter 5.4.2, “In-memory z/VM system loaded” on page 113, we describe the INSTPLAN command under step number 2 on page 115 that is run from the Integrated 3270 Console. The following information will be necessary.
INSTPLAN panels 1 and 2
Complete Table B-4 to record the values that are required in the first two INSTPLAN panels.
Table B-4 INSTPLAN values for the first two panels
|
Name
|
Value
|
Comment
|
|
Product install target
|
o F (SFS filepool)
o M (minidisk)
|
Leave set to the default value of F for all
|
|
Language
|
o AMENG
o UCENG
|
Select AMENG (American English)
|
|
DASD model
|
o 3390 10016
o 3390 _________
|
3390 10016 is a reference to 3390 Model-9. If you are installing to a larger disk size, overtype 10016 with the cylinder count for the disks you will use.
|
|
File pool name
|
VMPSFS
|
VMPSFS (default) recommended.
|
|
System type
|
o SSI (VMSSI)
o Non-SSI
|
|
|
Non-SSI system name
|
|
Used for non-SSI installation only.
|
|
Number of members
|
|
VMSSI installation only (usually 2 or 4).
|
|
SSI cluster name
|
|
VMSSI installation only.
|
|
Automatic configuration
|
NO
|
|
INSTPLAN panel 3
Complete Table B-5 to record the values that are required in the third INSTPLAN panel. The member names will become the z/VM system identifiers, and the logical partition (LPAR) names need to be the same names that are on the HMC.
Table B-5 INSTPLAN values for panel 3
|
Slot
|
Member name
|
LPAR name
|
Comment
|
|
1
|
|
|
Member 1 system identifier and LPAR name
|
|
2
|
|
|
Member 2 system identifier and LPAR name
|
|
3
|
|
|
Member 3 system ID and LPAR name (optional)
|
|
4
|
|
|
Member 4 system ID and LPAR name (optional)
|
INSTPLAN worksheet 3
Complete Table B-6 to record the volume labels and real device addresses that are required in the Installation Volume Definition INSTPLAN panel.
Table B-6 INSTPLAN values worksheet for volume definition
|
Type
|
Default
label
|
Chosen label
|
Address
|
Comment
|
|
COMMON
|
VMCOM1
|
|
|
Common volume 1
|
|
COMMON2
|
VMCOM2
|
|
|
Common volume 2
|
|
RELVOL
|
630RL1
|
|
|
Release volume 1
|
|
RELVOL2
|
630RL2
|
|
|
Release volume 2
|
|
Mem 1 RES
|
M01R01
|
|
|
Member 1 residence volume
|
|
Mem 1 SPOOL
|
M01S01
|
|
|
Member 1 spool volume
|
|
Mem 1 PAGE
|
M01P01
|
|
|
Member 1 page volume
|
|
Mem 1 WORK
|
M01W01
|
|
|
Member 1 work volume 1
|
|
Mem 1 WORK
|
M01W02
|
|
|
Member 1 work vol 2 (3390-3 only)
|
|
Mem 1 WORK
|
M01W03
|
|
|
Member 1 work vol 3 (3390-3 only)
|
|
Mem 2 RES
|
|
|
|
Member 2 residence volume
|
|
Mem 2 SPOOL
|
|
|
|
Member 2 spool volume
|
|
Mem 2 PAGE
|
|
|
|
Member 2 page volume
|
|
Mem 2 WORK
|
|
|
|
Member 2 work volume 1
|
|
Mem 2 WORK
|
|
|
|
Member 2 work vol 2 (3390-3 only)
|
|
Mem 2 WORK
|
|
|
|
Member 2 work vol 3 (3390-3 only)
|
|
Mem 3 RES
|
|
|
|
Member 3 residence vol (optional)
|
|
Mem 3 SPOOL
|
|
|
|
Member 3 spool volume
|
|
Mem 3 PAGE
|
|
|
|
Member 3 page volume
|
|
Mem 3 WORK
|
|
|
|
Member 3 work volume 1
|
|
Mem 3 WORK
|
|
|
|
Member 3 work vol 2 (3390-3 only)
|
|
Mem 3 WORK
|
|
|
|
Member 3 work vol 3 (3390-3 only)
|
|
Mem 4 RES
|
|
|
|
Member 4 residence vol (optional)
|
|
Mem 4 SPOOL
|
|
|
|
Member 4 spool volume
|
|
Mem 4 PAGE
|
|
|
|
Member 4 page volume
|
|
Mem 4 WORK
|
|
|
|
Member 4 work volume 1
|
|
Mem 4 WORK
|
|
|
|
Member 4 work vol 2 (3390-3 only)
|
|
Mem 4 WORK
|
|
|
|
Member 4 work vol 3 (3390-3 only)
|
INSTPLAN worksheet 4
Complete the worksheet in Table B-7 to record the common volume and channel-to-channel (CTC) addresses that are required in the INSTPLAN panel. This panel is shown at the end of 5.6.1, “Copying in-memory z/VM system to DASD” on page 124.
If only two members exist in the SSI, you need to specify only two pairs of CTCs (from member 1 to member 2, and vice versa).
Table B-7 INSTPLAN values worksheet for volume definition
|
Real addresses for the common volume on each member LPAR:
|
|||
|
Member 1
|
Member 2
|
Member 3
|
Member 4
|
|
|
|
|
|
|
CTC device addresses:
|
|||
|
From member 1
|
From member 2
|
||
|
To: member 1
|
N/A
|
To: member 1
|
_______ _______
|
|
To: member 2
|
_______ _______
|
To: member 2
|
N/A
|
|
To: member 3
|
_______ _______
|
To: member 3
|
_______ _______
|
|
To: member 4
|
_______ _______
|
To: member 4
|
_______ _______
|
|
From member 3
|
From member 4
|
||
|
To: member 1
|
_______ _______
|
To: member 1
|
_______ _______
|
|
To: member 2
|
_______ _______
|
To: member 2
|
_______ _______
|
|
To: member 3
|
N/A
|
To: member 3
|
_______ _______
|
|
To: member 4
|
_______ _______
|
To: member 4
|
N/A
|
z/VM networking resources
Complete the worksheet in Table B-8 to list the networking resources that will be needed when you start the IPWIZARD and when you create a VSWITCH for the Linux virtual machines.
Table B-8 z/VM and networking resources worksheet
|
Name
|
Value
|
Comment
|
|
TCP/IP user ID
|
|
TCPIP is recommended.
|
|
z/VM host name, member 1
|
|
|
|
z/VM host name, member 2
|
|
|
|
TCP/IP domain name
|
|
System domain name is usually set in DNS.
|
|
TCP/IP gateway
|
|
The router to and from the local subnet.
|
|
DNS server 1
|
|
Assigned by the network administrator.
|
|
DNS server 2/3
|
|
Optional.
|
|
Interface name
|
|
|
|
OSA starting device number
|
|
Start of OSA triplet for z/VM TCP/IP stack.
|
|
Subnet mask
|
|
Assigned by network administrator.
|
|
OSA device type
|
|
|
|
Maximum transmission unit (MTU) size
|
|
Check with network administrator.
|
|
Primary OSA device for virtual switch
|
|
Specify the first real device number and the next two device numbers will also be used.
|
|
Secondary OSA device for virtual switch
|
|
Ideally, it needs to be on a different channel-path identifier (CHPID)/OSA.
|
z/VM DASD worksheet
Use the worksheet in Table B-9 to document the z/VM DASD that you will use.
Table B-9 z/VM DASD blank worksheet
|
Device number
|
Label
|
Type
|
Notes
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Linux resources worksheet
Use the worksheet in Table B-10 to document the resources that are associated with the Network File System (NFS) server that will be used to be the installation source of the first Linux on z Systems.
Table B-10 Linux NFS server resources blank worksheet
|
Name
|
Value
|
Comment
|
|
TCP/IP address
|
|
|
|
User/password
|
|
|
|
NFS-exported installation directory
|
|
|
Use the worksheet in Table B-11 to document your Linux on z Systems resources.
Table B-11 Linux resources blank worksheet
|
Name
|
Value
|
Comment
|
|
Linux installation password
|
|
|
|
Linux root password
|
|
|
|
Linux TCP/IP gateway
|
|
|
|
Linux TCP/IP broadcast
|
|
|
|
Linux DNS server
|
|
|
|
Virtual Network Computing (VNC) installation password
|
|
|
Host names and IP addresses worksheet
Use the worksheet in Table B-12 to document the host names and associated IP addresses and virtual machines that you will use.
Table B-12 Host names blank worksheet
|
Host name
|
IP address
|
Virtual machine/LPAR
|
Notes
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.