ZL002 Xinst

V11.
cover
Front cover
Instructor Exercises Guide
z/VM and Linux on IBM Z and LinuxONE
Bootcamp
Course code ZL00G ERC 2.0
Global Learning and Skills Engineering

V11.3
Contents
TOC
Contents
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Instructor exercises overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Exercises description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Exercise 1. z/VM log on overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Exercise 2. z/VM installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Part 1: Installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Part 2: Preparing to install your z/VM 7.1 non-SSI system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Part 3: Installing your z/VM 7.1 non-SSI system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Part 4: Editing files on the z/VM system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Part 5: Updating the PROFILE XEDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Part 6: Moving PROFILE XEDIT to the system disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Exercise solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Exercise 3. 7.1 CP system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Part 1: Starting the z/VM guest operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Part 2: Accessing the PARM disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Part 3: Update system logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Part 4: Modifying the SYSTEM CONFIG file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Part 5: Formatting and allocating CP volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Part 6: SALIPL EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Part 7: Testing your changes to the SYSTEM CONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Part 8: Backing up your changes to SYSTEM CONFIG on the back-up PARM disk . . . . . . . . . . . . 3-7
Exercise solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Exercise 4. z/VM User Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Part 1: Log on and start up your z/VM guest system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Part 2: Locating the system directory file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Part 3: Running the Diskmap exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Part 4: Adding users to the USER DIRECT file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Part 5: Putting the updated directory online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Part 6: Testing your new virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Exercise 5. z/VM networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Part 1: Log on and start up your z/VM guest system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Part 2: Directory modifications for TCPIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Part 3: Tailoring TCPIP, using IPWIZARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Part 4: Logging on to TCPMAINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Part 5: Tailoring the DTCPARMS file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Part 6: Tailoring the TCPIP DATA file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Part 7: Tailoring the PROFILE TCPIP file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Part 8: Automating the startup of the TCP/IP virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Part 9: Starting the TCP/IP virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Part 10: Testing the TCP/IP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
© Copyright IBM Corp. 2007, 2018 ii

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
V11.3
Contents
TOC Exercise 6. Servicing z/VM (VMSES/E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Part 1: Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Part 2: Load the service files from the RSU or COR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Part 3: Install the RSU envelope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Part 4: Place the service into production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Part 5: Install a COR envelope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Part 6: Place the service into production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Exercise 7. Linux installation on IBM Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Part 2: Prepare the environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Part 3: Transfer the Linux boot files to minidisk A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Part 4: Prepare the files for the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Part 5: Start the installation on z/VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Exercise 8. Linux networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Part 2: Validating environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Part 3: Using s390-tool to configure the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Exercise 9. Linux system management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Part 1: Add Vdisk dynamically for swap space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Part 2: Add the disk permanently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Part 3: Using cpuplugd to manage CPU resources automatically . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Exercise 10. z/VM Performance Toolkit configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Part 1: Log on to the student guest system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Part 2: Full screen console mode for the system operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Part 3: Enable and configure Performance Toolkit for z/VM 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Part 4: Performance Toolkit System Management Facility web interface . . . . . . . . . . . . . . . . . . . 10-5
Part 5: Web interface testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Exercise A. z/VM 7.1 installation worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
© Copyright IBM Corp. 2007, 2018 iii

V11.3
Trademarks
TMK
Trademarks
The reader should recognize that the following terms, which appear in the content of this training
document, are official trademarks of IBM or other companies:
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide.
The following are trademarks of International Business Machines Corporation, registered in many
jurisdictions worldwide:
developerWorks® IBM Spectrum™ System z®
DirMaint™ IBM z Systems® Tivoli®
ECKD™ Language Environment® VTAM®
FICON® PR/SM™ z Systems®
FlashCopy® RACF® z/Architecture®
HiperSockets™ Redbooks® z/OS®
IBM LinuxONE™ RMF™ z/VM®
IBM Spectrum Protect™ S/390® z/VSE®
Adobe is either a registered trademark or a trademark of Adobe Systems Incorporated in the United
States, and/or other countries.
Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United
States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other
countries, or both.
Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of
Oracle and/or its affiliates.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other product and service names might be trademarks of IBM or other companies.
© Copyright IBM Corp. 2007, 2018 iv

V11.3
Instructor exercises overview
pref
Instructor exercises overview
After completing the exercises, students should be able to:
• Install and Configure z/VM and additional subsystems
• Install and Configure Linux on IBM Z
• Apply Service to z/VM 7.1
• Manage TCPIP for z/VM and Linux on IBM Z
• Back up and Restore files with TSM Linux on IBM
Each exercise depends on successful completion of the previous exercises.
© Copyright IBM Corp. 2007, 2018 v

V11.3
Exercises description
pref
Exercises description
This course includes the following exercises:
• z/VM log on overview
• z/VM installation
• 7.1 CP system configuration
• z/VM User Directory
• z/VM networking
• Servicing z/VM (VMSES/E)
• Linux (RedHat, SUSE, and Ubuntu) installation on IBM Z
• Linux networking
• Linux system management
• z/VM Performance Toolkit configuration
In the exercise instructions, you can check off the line before each step as you
complete it to track your progress.
Most exercises include required sections that should always be completed. It
might be necessary to complete these sections before you can start later
exercises.
© Copyright IBM Corp. 2007, 2018 vi

V11.3
Exercise 1. z/VM log on overview
EXempty
Estimated time
00:30
Instructor Information: You must have the students complete this exercise
because the next exercise does not cover having the student log on.
Overview
This exercise describes the process of logging on to the student IDs to perform
the student exercises.
Objectives
At the end of the exercise, you should be able to:
• Log on to the VM system by using the logon BY option
© Copyright IBM Corp. 2007, 2018 1-1

Samon: Log on screen

Netid= USIBMES IBM Training Terminal= SLIP7051
Host = ESSCMC2 MOP CLPz PAGE 1
To Disc = LOGOFF 20:36 Wednesday - August 29, 2013
APPLNAME STATUS | APPLNAME STATUS | APPLNAME STATUS
--------------------------------------------------------------------------------
TSOE UP 09:05 | |
VM2 UP 09:05 | |
ESSMVS1 UP 09:05 | |
MOPEDVM1 UP 09:05 | |
MOPEDVM2 UP 09:05 | |
ESSMVS7 UP 09:05 | |
XTSOE UP 09:05 | |
CMC1 UP 09:05 | |
CMC2 UP 09:05 | |
NVMVS UP 04:31 | |
NVCMC1 UP 05:11 | |
NVCMC2 UP 09:05 | |
MVS1U DOWN 09:05 | |
--------------------------------------------------------------------------------
Help Desk (001)404-238-6000 CLPHELP@US.IBM.COM (888)502-5511(TL 888-6000)
IBM Mgt Approved Usage Only
==>
PF1=Help PF2=ESSMVS1 PF3=Return PF4=VM2 PF7=Backward PF8=Forward
© Copyright IBM Corporation 2007, 2018

Notes:
This is the first screen that you should see.
This displays the IBM Learning Services Samon Screen.
From this screen, you enter MOPEDVM2 (or press PF4).

V11.3
EXempty
MOPEDVM2: System logo

z/VM ONLINE
==== ======== ==== ====

==== ========= ===== =====
== == == ===== =====
== ======== ====== ======
== ======== == ======= ==
== == == == ===== ==
==== ========= === === === MOPEDVM2
==== ======== === = === z/VM
6.1.0
IBM Training
Montpellier - France
(T/L 888-6000...404-238-6000)
Use of this system is for IBM
Management approved purposes only.
Fill in your USERID and PASSWORD and press ENTER

(Your password will not appear when you type it)
USERID ===>
PASSWORD ===>
COMMAND ===>
RUNNING MOPEDVM2
Samon: Log on screen © Copyright IBM Corporation 2007, 2018
Notes:
This is the LOGO screen for MOPEDVM2.
Press the Enter key to display the second logon screen, where you enter a special version of the
logon command.

Log on with the BY option

Enter one of the following commands:
LOGON userid (Example: LOGON VMUSER1)

DIAL userid (Example: DIAL VMUSER2)
MSG userid message (Example: MSG VMUSER2 GOOD MORNING)
LOGOFF
logon ZVMB21 by SZVMB21

CP Read MOPEDVM2
Notes:
The MOPEDVM2 system programming staff requires that we use the logon BY option when we run
second-level guest systems.
The syntax is:
log on ZVMBnn BY SZVMBnn
where nn is the team number that is given to you by your instructor. In other words, Team21 uses
ZVMB21, Team22 uses ZVMB22, and so on).
You will be prompted for your password after you press Enter.

V11.3
EXempty
Password prompt
logon zvmd01 by szvmd01
Enter your password,

or
To change your password, enter: ccc/nnn/nnn
where ccc = current password, and nnn = new password
XXXXXX
CP Read MOPEDVM2
Notes:
At the logon prompt for your SZVMBnn userid, enter the password that was provided to you by your
instructor.
The password expires the first time that you enter it, so you must change that password. Read the
instructions on the screen for changing your password. Your instructor will provide you with your
new password.

TCP/IP lab introduction: Network connections
A000- A010- A000- A010- A010- A000-

A002 A012 A002 A012 A012 A002
ZVMB21 ZVMB22 ZVMB2n
Notes:
Each student team has two OSA connections to the network.
Each connection consists of three addresses that are defined to each student team. The addresses
are virtual A000- A002 and A010 - A012.
Good luck in the class.
End of exercise

V11.3
Exercise 2. z/VM installation
EXempty
Estimated time
03:00
Overview
The students will log on to their z/VM virtual machine and install a z/VM 7.1 guest
operating system. They will use the planning worksheets in Appendix A to plan the
installation, and then run the z/VM utilities to complete the installation.
Objectives
At the end of the lab, you should be able to:
• Install a z/VM 7.1 non-SSI system
• Complete the installation worksheets
• Use the installation planning utilities
• Use the installation utilities
Requirements
• Student lab virtual machine
• Terminal with access to the lab z/VM system
• Student Notebook and Exercise Guide
Instructor exercise overview

The instructor should perform this lab exercise to be familiar with all the steps the students are
going to perform.

Exercise instructions
The LAB environment that you use for exercises runs in an LPAR. z/VM runs there (ID:
POKEDVM2) and hosts a number of Virtual Machines (VMs). Each team has its own VM (ID:
ZVMBxx) for the LAB exercises.
The first time that you log on to your VM (by using the bottom 3270 screen that is shown above),
you run CMS in first level. This approach enables you to install z/VM in second level in that VM.
When the second-level z/VM is running in your VM (wiping out CMS), you are still logged on to
ID: ZVMBxx. But you can log on to the second-level z/VM (by using the upper 3270 screen above).
At the second level, you can access any VM defined in the second-level z/VM, including a VM for
bootstrapping a Linux installation.
When you see the logon screen for second level, you can toggle between first level and second
level by using PA1. You see the VM ID changing in the bottom-right corner of the screen. It is
possible to DISCONNECT from second level when you see the first-level VM ID, POKEDVM2, and
get back into second-level VM using DIAL ZVMBxx from the first level logon screen. However, you
have to issue CP ENABLE ALL on the second level before using the DIAL command.
If you are in second level using the DIAL command, you cannot use PA1 to toggle between first
level and second level.
Part 1: Installation requirements

Your guide for this lab exercise will be Chapter 2, Chapter 4, and Chapter 9 of the z/VM Installation
Guide. This guide is found on the CD provided in your student materials.
__ 1. Begin in Chapter 2. “Plan your traditional installation” (page 7 of the z/VM Installation
Guide). Briefly review Steps 1 and 2. (You will be doing a second-level installation from an
FTP server.) Use the tables in the student exercise Appendix for Step 3 to complete the
installation worksheets on page 16 and 17.

V11.3
EXempty
__ 2. Use the following information to fill out the worksheets:
__ a. Choose the Second-level Installation method.
__ b. Install all products/components to VMSYS filepool [F].
__ c. Default system language will be AMENG.
__ d. Use 3390 10016 CYL DASD.
__ e. The common shared file pool name will be ZVMBnn, where nn is your team number.
__ f. The installation type is Non-SSI.
__ g. Your system name will be ZVMBnn.
__ h. We will NOT use SMAPI client for system management.
__ i. Use the DEFAULT volume labels for your DASD initialization, and addresses 123-127.
__ j. You will install from an FTP SERVER (10.31.189.239).
__ k. FTP user/password ==> ZVM06V8/ zvm068 (the user name is in uppercase, password
is lowercase).
__ l. FTP directory will be /ZVM71/CPDVD.
__ 3. In Step 4. “Chose your next step,” choose “Traditional installation for second level.”
Part 2: Preparing to install your z/VM 7.1 non-SSI system

__ 4. In Chapter 4, select the option to install from an FTP server directory.
__ 5. Perform the steps in Step 2a. “Set up the user ID for installation” (page 32)
Note: Skip substep 1, because the DVD is already loaded to the FTP server directory. Also,
for substep 2 you should already be logged on to your first level user ID (from Exercise 1).
But if not, follow the steps in Exercise 1 to log on to your first level virtual machine.
__ 6. If your machine displays VM READ in the bottom right corner of the display, press Enter.
__ 7. Your status area should now display RUNNING. (This means that the virtual machine is
either doing work or prepared to do so.) So you are in position to proceed with substep 3.
__ 8. For substep 5, the first-level system in the lab environment is a 6.4 system, so you would
want to access MAINT’s 2CC disk. However, this is a shared instructional system, and you
do not have access. So the INSTPIPE MODULE has been copied to your 192 disk. Access
your 192 disk as filemode “C” and for now use that disk as if it were MAINT’S 2CC disk.
__ 9. In substep 6-b, you will use the IP address of the FTP server, userid, and password from
your worksheets you completed in Step 2.
__ 10. Detach the 192 disk.
What command did you use? _______________________
Instructor note: Pipe ftpget -h 10.31.189.239 -u ZVM06V8 -p zvm068 -d /ZVM71/CPDVD -v
BEF -DVDEOF -f CKD222* |UNPACK| ECKDREST 2222
__ 11. Complete Step 2b. “Run DVDPRIME” in the Installation Guide.
Hint: Keep in mind that the directory is case-sensitive (it is a Linux for IBM Z environment).

__ 12. When DVDPRIME is complete, you must follow the Installation Guide to perform the
Non-SSI DVD installation (Chapter 5, page 45).
Part 3: Installing your z/VM 7.1 non-SSI system

__ 13. Fill out the INSTPLAN panels by using the worksheets that you completed previously and
make sure that you select the option to FORMAT THE VOLUMES.
__ 14. Make sure that you get the following message when you finish:
IUGINP8392I INSTPLAN EXEC ENDED SUCCESSFULLY
__ 15. In Step 2, “Verify the volumes that are needed for installation are available,” substep 1 (page
51) make sure that you skip to substep 8.
__ 16. In Step 2, substep 8, since you are using CKD minidisks (you do NOT attach minidisks),
skip this step. The minidisks are already ATTACHED.
__ 17. Issue Query V 123-127
Did you see your volumes? ___________________
__ 18. Execute Step 3. “Run INSTALL” to install your new system (page 52). This is going to take a
little while to run. The screen clears automatically.
__ 19. Issue the command #cp msg * test.
What virtual machine is performing this portion of the installation? ______________
The rest of the installation process will take 30 - 40 minutes, so this is a good time to go for
a coffee break.
After many userids’ minidisks are loaded, the installation process will automatically IPL the
new system.
__ 20. If the INSTALL exec is still running when you return from your break:
Again issue the command #cp msg * test.
What virtual machine is performing this portion of the installation? __________
Depending on when you returned, you might see that a couple of disks are being restored
with DDR.
Next, you would see the shared file system servers that are being initialized.
When the shared file system servers are initialized, you would see the service process start.
An RSU is shipped with your installation code and will automatically be installed and put into
service. We will discuss this process in a later chapter in this course.
__ 21. When the service process completes, the new system is IPLed. This time you will need to
clear the screen for it to continue.
When the IPL is complete, see Step 4. “Log on to the new system” (page 57 of the
Installation Guide).
Note: Congratulations! You have successfully installed the z/VM 7.1 in second level. The next
steps will be working with the second-level z/VM 7.1 system.

V11.3
EXempty
__ 22. Issue the CP command Query CPLEVEL.
What is your CPLEVEL? _________________________________
__ 23. Issue the LOGOFF command and log on to the MAINT virtual machine by using the
surrogate userid IBMVM1. The default password is the same as MAINT710. When you log
on to MAINT, you must press Enter until you see RUNNING in the bottom right of your
screen.
__ 24. Press the PA1 key to return your virtual machine to first level (with PCOMM this is mapped
to the ESC key by default). Enter #cp link * 192 192 mr. Clear your screen (the clear
key by default is mapped to the PAUSE key) until you return to your second-level system.
You should see ZVMBnn in the bottom right corner when you complete this task.
__ 25. We will now work with XEDIT and setting up the MAINT virtual machine to your liking.
Part 4: Editing files on the z/VM system

__ 26. Enter the following command:
xedit profile exec a
You will see that the file PROFILE EXEC is displayed based on the system defaults for
XEDIT.
Do you like the way your edit session is being displayed? __________________
Probably not. So let's look at this file using a different set of edit defaults.
__ 27. Press the F3 key on your keyboard to exit from this file (F3 is set to the XEDIT command
QUIT).
__ 28. As mentioned previously, you have a DASD volume at address 192 that contains several
files for use in the exercises. You just relinked this disk at first level, and now you will attach
this disk to your MAINT virtual machine. Use the CP command ATTACH and attach this
volume to your virtual machine as address FFF.
Note: If you are unsure of the syntax, type Help CP ATTACH.
When you complete this step, access the new volume as drive letter Z.
Note: This is not a CP command, so for syntax assistance for this command, type HELP
ACCESS.
__ 29. Issue the following command: copy student xedit z profile = a2 (This will copy
the student XEDIT file on your A-disk to a file called profile XEDIT on your A-disk).
Was this successful? ___________ (Use the HELP facility if needed.)
__ 30. Issue the command again with the additional required parameter of replace to copy the file.
__ 31. Now reissue the command to display your PROFILE EXEC file again: xedit profile
exec a
Do you like the way your edit session is being displayed now? ______________
This might not be exactly what you want, but it is probably much better, and in this lab we
will make updates to the file that controls your XEDIT session. But for now let's do a couple
of things to this file.

__ 32. Locate the command in this file that sets a function key to RETRIEVE BACKWARD. Then,
change the PFnn to the PF key you wish to use to retrieve commands when you are in the
CMS and CP environment. If you don’t locate it, you can define in the next steps.
__ 33. Replicate that line and set another PF key to issue the FILELIST command.
__ 34. The final modification for the PROFILE EXEC is to add the following statements:
'CP SET PF12 RETRIEVE BACKWARD'
'CP TERM MORE 3 2 '
'CP TERM HOLD OFF'
'CP SET RUN ON'
These commands will cause your screen to clear automatically when it fills up, and will allow
your virtual machine to keep running programs even when it becomes disconnected.
Enter FILE on the command line (top of screen ====>) and press Enter. More on this later
but we discussed it in the lecture.
Part 5: Updating the PROFILE XEDIT

__ 35. Enter the following command: XEDIT PROFILE XEDIT.
This file, as discussed in the lecture, sets the defaults for your XEDIT session. We will
modify this file to set up the XEDIT session in a manner that you prefer.
__ 36. We need to discuss the LOCATE command before we continue.
__ a. Issue the command HELP XEDIT MENU. This will display the list of XEDIT commands
that are available to you in your XEDIT session.
__ b. Move your cursor to the LOCATE command and press Enter.
__ c. Read Usage Note 4 about specifying target character strings. After you have read the
information about this command, return to the XEDIT session and use LOCATE to find
PF1 and see what it does.
Some HELP files open in Brief Help, and some open in Full Help. In some files, you may
be able to toggle back and forth between Brief and Full Help displays with PF1.
__ d. Open a help session for a command and experiment with the PF3 and PF4 keys to see
that they perform differently when exiting from the Help facility.
Which PF key brings you back one level? ___________________
Which PF key returns you back to your XEDIT sessions? ______________
Now let’s make some usability modifications to the PROFILE XEDIT file. Let's start with
the command line.
Where would you like to have it located? ______________
__ 37. Issue the appropriate command to locate all the lines that have the word CMDLINE in them.
(Hint: If you get stuck, try HELP ALL.)
__ 38. Now set the command line to top or bottom. You may also wish to modify the line color.
__ 39. Make these changes. Then enter the ALL command without parameters on the command
line to redisplay all the lines that were hidden when you used the ALL macro with the locate
command.

V11.3
EXempty
__ 40. Next, do you wish the scale to be displayed? If so, make the appropriate change.
__ 41. Do you want the prefix area and numbers on the left or right? Make the appropriate change
to this file to set the prefix area where you want it.
__ 42. Now we need to see what we can do to make XEDIT automatically save our working
session. There is a SET command called AUTOSAVE. You can look at the Help facility, but
there is a different way to find the syntax. Issue the command MODIFY AUTOSAVE on the
command line and see what happens. You will see that it is set to the default OFF. The other
option is to set it to a numeric value that will represent how often you wish to automatically
save your changes.
__ 43. Now that you know the syntax for AUTOSAVE add this command to your PROFILE XEDIT
file on the previously inserted blank line.
__ 44. We probably should have put the AUTOSAVE statement with the rest of the XEDIT SET
statements. Let's do that now. Move your AUTOSAVE statement to the area in the file with
all the other general set commands at the top. Use the Help facility if needed.
__ 45. Locate all the lines that have the words PREFIX SYNONYM in them.
You can look at help to see what this does. This is very helpful in making your XEDIT
session similar to other editors with which you may be more familiar. In this file, we are
setting the prefix area command A (after) to be the same as F (following - the XEDIT target
command for a copy or move operation). We have also done the same thing for line
replication changing the “ to R and ““ to RR, and so on.
__ 46. File all of your changes and then XEDIT the PROFILE XEDIT file again to check your
modifications. If you have error messages that are displayed at the top of your screen, try to
fix them or ask for assistance from your instructor.
__ 47. Close your XEDIT session when you are satisfied with your work.
__ 48. XEDIT your SYN SYNONYM file on MAINT’s 191 disk. Add more synonyms that would help
you do your job (see the following examples). This file must be in uppercase.
SYN SYNONYM A1 F 80 Trunc=80
====>
* * * Top of File * * *
FILELIST FL
PEEK PE
RECEIVE REC
REPLACE REP
* * * End of File * * *
__ 49. File your changes when you are satisfied with your updates
Part 6: Moving PROFILE XEDIT to the system disk

In the previous step, if you had not been provided with a sample file you would have had to enter all
those commands into the PROFILE XEDIT file manually. Since you will be the system programmer
for the z/VM system, it would be considerate of you to make this file available to everyone that logs
on to the system. This can be done easily if you have the proper authority and privileges. Since you
are logged on to the MAINT virtual machine, you have all of those privileges (and responsibilities).

The MAINT virtual machine is one of the most powerful userids on the system. This user owns
several minidisks that are linked to by all other CMS userids on the system for the sharing of files
and programs. If you copy the PROFILE XEDIT file you have modified to MAINT's 190 disk, then it
will be available for everyone on the system. Let's see what it takes to perform this task. While easy,
it is slightly more involved than just copying the file to the disk.
__ 50. First, clear your screen.
__ 51. Issue the command QUERY DISK. This is a CMS command that displays what disks this
virtual machine currently has accessed and available to CMS. Pay special attention to the
190 - S disk. You should have seen that this disk is accessed in read only mode.
__ 52. Issue the command QUERY VIRTUAL 190. This is a CP command and it should have
shown that you have it linked in READ/WRITE mode.
So what is the deal here? __________________________________
You actually have ownership of this disk in READ/WRITE mode, just as CP says. But the S
Disk is a special disk, and when CMS IPLs it always accesses this disk in READ ONLY
mode. So if we want to copy a file to this disk we need to access it in READ/WRITE mode.
This is easier than you might think.
__ 53. Issue the following command: ACCESS 190 Z.
__ 54. Now issue the QUERY DISK command again and see the status of the Z disk.
READ ONLY or READ/WRITE? _______________
You should have the Z disk in READ/WRITE mode and now we can copy files to this disk.
__ 55. Issue the following command:
COPY PROFILE XEDIT A = = Z2 (OLDDATE
(You must use the z2 on the command. The instructor will explain this in the lab review.)
__ 56. We also need to put this file on the 490 disk. Log off from MAINT and log on to MAINT710
(same password as MAINT).
__ a. Issue the command ACCess 490 Z.
__ b. Then, COPY PROFILE XEDIT S = = Z2 (OLDDATE
Now that you have this file on the 190 and 490 disks, we have a few more tasks to
complete. But first let’s see the message that was caused by accessing MAINT's 190 disk in
write mode and making modifications to a file there.
__ c. Issue the IPL CMS PARM AUTOCR command.
Did you see a warning message about the DMSWSP100W Shared S-STAT not available?
__________________________
__ d. To correct this problem, issue the following command:
PUT2PROD SAVECMS
__ 57. Shut down your second-level z/VM 7.1 system with the SHUTDOWN command.
__ 58. You should see the z/VM shutdown messages on the console, when you get the message
HCPGIR450W CP entered; disabled wait PSW, log off the first-level system.
You have successfully completed this lab exercise.

V11.3
EXempty
End of exercise

Exercise solutions
Part 2: Preparing to install your z/VM 7.1 non-SSI system
Step 10: Detach the 192 disk. What command did you use? DETACH 192.

V11.3
EXempty
Step 18: Did you see your volumes? YES
Step 20: Run the INSTALL exec and watch for a while and then go for a coffee break.
IUGIIS8490I NOW FORMATTING VOLUME 0123 (1 OF 10)
IUGILB8440I NOW LOADING MAINT CF1 (CF1) DISK 1 OF 190
IUGILB8440I NOW LOADING MAINT CFD (CFD) DISK 2 OF 190
IUGILB8440I NOW LOADING MAINT CF3 (CF3) DISK 3 OF 190
IUGILB8440I NOW LOADING MAINT 190 (190) DISK 4 OF 190
IUGILB8440I NOW LOADING PMAINT CF0 (CF0) DISK 5 OF 190
IUGILB8440I NOW LOADING PMAINT 2CC (2CC) DISK 6 OF 190
IUGILB8440I NOW LOADING PMAINT 1CF0 (909) DISK 7 OF 190
IUGILB8440I NOW LOADING MAINT630 CF2 (CF2) DISK 8 OF 190
IUGILB8440I NOW LOADING MAINT630 191 (191) DISK 9 OF 190
IUGILB8440I NOW LOADING MAINT630 4CC (4CC) DISK 10 OF 190
IUGILB8440I NOW LOADING BLDCMS 191 (8D1) DISK 11 OF 190
IUGILB8440I NOW LOADING BLDNUC 191 (8AD) DISK 12 OF 190
IUGILB8440I NOW LOADING BLDRACF 191 (8AC) DISK 13 OF 190
IUGILB8440I NOW LOADING BLDSEG 191 (8A9) DISK 14 OF 190
***** 311 additional messages about LOADING Disks *********
IUGIDV8341I USER DIRECTORY HAS BEEN BROUGHT ONLINE SUCCESSFULLY
IUGIDV8341I SALIPL COMMAND HAS COMPLETED SUCCESSFULLY
IUGIWF8341I {MDDUMP|ECKDDUMP} OF 2CF0 COMPLETED SUCCESSFULLY
IUGIWF8338I NOW EXECUTING COPY OF 24CC TO 4CC STEP
IUGIWF8341I {MDDUMP|ECKDDUMP} OF 24CC COMPLETED SUCCESSFULLY
IUGIDV8392I INSTDVD EXEC ENDED SUCCESSFULLY
******************************************
NOW IPLing VOLUME 125
WITH COMMAND:
CP SYSTEM CLEAR
TERMINAL CONMODE 3270
SET MACHINE ESA
IPL 125 CLEAR
******************************************
10:28:40 z/VM V7 R1.0 SERVICE LEVEL 1801 (64-BIT)
10:28:41 SYSTEM NUCLEUS CREATED ON 2018-10-29 AT 10:48:03, LOADED FROM M01RES
10:28:41
*********************************************************************************
10:28:41 * LICENSED MATERIALS - PROPERTY OF IBM* *
10:28:41 * *
10:28:41 * 5741-A07 (C) COPYRIGHT IBM CORP. 1983, 2013. ALL RIGHTS *
10:28:41 * RESERVED. US GOVERNMENT USERS RESTRICTED RIGHTS *

10:28:41 * DUPLICATION RESTRICTED BY GSA ADP SCHEDULE *

10:28:41 * CONTRACT WITH IBM CORP. *
10:28:41 * *
10:28:41 * * TRADEMARK OF INTERNATIONAL BUSINESS MACHINES. *
10:28:41 ************************************************************************
10:28:41 HCPZCO6718I Using parm disk 1 on volume VMCOM1 (device 0123).
10:28:41 HCPZCO6718I Parm disk resides on cylinders 1 through 120.
10:28:41 The directory on volume M01RES at address 0125 brought online
10:28:41 HCPWRS2513I Spool files available 29
10:28:42 HCPWRS2512I Spooling initialization is complete.
10:28:42 DASD 0128 dump unit CP IPL pages 9871
10:28:42 HCPMLM3016I Management by the Unified Resource Manager is not for this
system.
10:28:42 HCPAAU2700I System gateway ZVMBnn identified.
10:28:42 HCPLNM101E DASD 0CF1 forced R/O; R/O by SYSTEM; stable by SYSTEM
10:28:42 HCPLNM101E DASD 0CF3 forced R/O; R/O by SYSTEM; stable by SYSTEM
10:28:42 z/VM Version 6 Release 3.0, Service Level 0000 (64-bit),
10:28:42 built on IBM Virtualization Technology
10:28:42 There is no logmsg data
10:28:42 FILES: NO RDR, NO PRT, NO PUN
10:28:42 log on AT 10:28:42 EDT TUESDAY 08/06/13
10:28:42 GRAF 0020 log on AS MAINT630 USERS = 1
10:28:42 HCPIOP952I 0096M system storage
10:28:42 FILES: 0000002 RDR, 0000001 PRT, NO PUN
10:28:42 HCPCRC8082I Accounting records are accumulating for userid DISKACNT.
z/VM V6.3.0 2013-05-29 10:47
10:29:37 AUTO log on *** OP1 USERS = 2 BY MAINT630
10:29:37 HCPCLS6056I XAUTOLOG information for OP1: The IPL command is verified by
the IPL command processor.
z/VM DASD DUMP/RESTORE PROGRAM

HCPDDR698I DATA DUMPED FROM 0X0100 TO BE RESTORED
HCPDDR697I NO VOL1 LABEL FOUND
RESTORING 0X0100
DATA DUMPED 04/11/13 AT 18.12.19 GMT FROM 0X0100 RESTORED
INPUT CYLINDER EXTENTS OUTPUT CYLINDER EXTENTS
START STOP START STOP
0 3329 0 3329
END OF RESTORE
BYTES RESTORED 2461676300
END OF JOB
z/VM DASD DUMP/RESTORE PROGRAM
HCPDDR698I DATA DUMPED FROM 0X0100 TO BE RESTORED
HCPDDR697I NO VOL1 LABEL FOUND
RESTORING 0X0100
DATA DUMPED 04/11/13 AT 18.12.19 GMT FROM 0X0100 RESTORED

V11.3
EXempty
INPUT CYLINDER EXTENTS OUTPUT CYLINDER EXTENTS
START STOP START STOP
0 3329 0 3329
END OF RESTORE
BYTES RESTORED 2461676300
IUGPLD8341I POSTLOAD PROCESSING STARTED

DMSACC724I 4CC replaces C (4CC)
IUGIFP8493I ISSUING XAUTOLOG FOR VMSERVU

AUTO log on *** VMSERVU USERS = 3
HCPCLS6056I XAUTOLOG information for VMSERVU: The IPL command is verified by the
IPL command processor.
IUGIFP8493I ISSUING XAUTOLOG FOR VMSERVR

AUTO log on *** VMSERVR USERS = 3
HCPCLS6056I XAUTOLOG information for VMSERVR: The IPL command is verified by the
IUGIFP8493I ISSUING XAUTOLOG FOR VMSERVS
AUTO log on *** VMSERVS USERS = 4
HCPCLS6056I XAUTOLOG information for VMSERVS: The IPL command is verified by the
USER DSC LOGOFF AS VMSERVR USERS = 4 FORCED BY MAINT630
IUGIFP8493I ISSUING XAUTOLOG FOR VMSERVR
IUGIFP8493I ISSUING XAUTOLOG FOR VMSERVP

AUTO log on *** VMSERVP USERS = 6
HCPCLS6056I XAUTOLOG information for VMSERVP: The IPL command is verified by the
IUGIFP8338I UPDATING SYSTEM TABLES AND CLEANING UP FILEPOOL DIRECTORIES

USER DSC LOGOFF AS VMSERVP USERS = 5 FORCED BY MAINT630
DASD 0917 DETACHED
IUGIUF8493I ISSUING XAUTOLOG FOR VMSERVP

AUTO log on *** VMSERVP USERS = 6
HCPCLS6056I XAUTOLOG information for VMSERVP: The IPL command is verified by the
Service processing started

**********************************************************
* NOW EXECUTING SERVICE ALL 7101RSU
**********************************************************
***** SERVICE messages *****************
**********************************************************
* NOW EXECUTING PUT2PROD *

**********************************************************
****** PUT2PROD messages ***************
*********************************************************************************
* INSTCOMP NOW ISSUING SHUTDOWN REIPL *
*********************************************************************************
SYSTEM SHUTDOWN STARTED
Step 21: What virtual machine is performing this portion of the installation? MAINT710
Step 22: What is your CPLEVEL? z/VM Version 7 Release 1.0, service level 1801 (64-bit).

V11.3
Exercise 3. 7.1 CP system configuration
EXempty
Estimated time
02:30
Overview
In this exercise, students have the opportunity to modify system definitions. The
students will access the PARM disk in write mode, modify the system
configuration file, execute CPFMTXA, and test their changes.
Objectives
• Release the PARM disk from CP
• Relink and reaccess the PARM disk in write mode
• Use XEDIT to modify the SYSTEM CONFIG file
• Run the CPSYNTAX program to check for mistakes
• Execute the CPFMTXA program to create disks usable by CP
• Shut down and restart the system to test those changes
Requirements

going to perform.

V11.3
EXempty
Part 1: Starting the z/VM guest operating system
__ 1. Log on to your team virtual machine.
__ 2. Set up and IPL your z/VM system. Use the same procedure from previous exercises. (That
is, system reset / term conmode 3270 / ipl 125 clear loadparm 020 / warm start.) Then
DISCONNECT from the OPERATOR. In later exercises, we will refer to this as Set up and
IPL your z/VM system.
__ 3. Press PF10 to load z/VMsystem.

__ 4. Issue DISCONNECT and you should see the system logo for the z/VM system. Log MAINT
by ibmvm1 from the command line of this screen userid MAINT.
__ 5. Issue the command CP QUERY NAMES to see the virtual machines that are currently logged
on.
Part 2: Accessing the PARM disk

__ 6. Issue the following: QUERY CPDISK.
This command displays all the disks that where accessed by CP at IPL time. You should
see the CF1 disk in this list.
__ 7. You must access the PARM disk in write mode to update the logo files. Because the system
accesses the PARM disk in SR mode at IPL time, you have several steps to perform.
What does SR mode imply? ____________________________________
Issue the following commands:
cprelease a
link maint cf1 cf1 mr
access cf1 z
filelist * * z

V11.3
EXempty
Part 3: Update system logo
__ 8. You need to access the shared filesystem where the DRAWLOGO is with the command
ACC VMPSFS:MAINT710.CPDV.SAMPLE F (FORCERW
Note: You can log on to MAINT710 and access drawlogo from there by issuing this command:
VMFSETUP SERVP2P CPSFS (RETAIN Z (if shared filesystem used during the
z/VM installation)
or
VMFSETUP SERVP2P CP (RETAIN Z (if minidisk used during the z/VM
installation)
__ 9. List all of the files on the F disk. (Remember that you can use the synonym that you set up
previously for this command.) You should see two files that are called
DRAWLOGO SAMPEXEC and X$DRWL$X SAMPXEDI.
__ 10. Copy the DRAWLOGO file to a file type of EXEC (keeping the same file name).
__ 11. Copy the X$DRWL$X file to a file type of XEDIT (keeping the same file name).
__ 12. Press PF2 to refresh the filelist display and verify that your new files were created.
__ 13. Run DRAWLOGO against the LOCAL LOGO file on the Z disk. Make as many changes as
you like to the logo (maybe add colors or blinking, and so forth). Be sure to display your
results.
__ 14. Go to PARM DISK CF1 previously accessed and do the following steps:
copy local logo z local logobkp z
copy local logo f = = z (oldd rep
__ 15. In order to restore the PARM disk access to CP, Issue the following commands:
link maint cf1 cf1 rr
cpaccess maint cf1 a
q cpdisk
Part 4: Modifying the SYSTEM CONFIG file

__ 16. Link PMAINT’s CF0 disk in MR mode, and access it as filemode Z.
__ 17. Before you make any changes to the SYSTEM CONFIG file, make a backup copy on the
CF0 disk. Make the new filename OLDSYS and keep the filetype CONFIG.
What command did you use? _______________________________________
__ 18. List all the files on the “Z” disk to verify that your copy command worked as you expected
and then edit the SYSTEM CONFIG Z file.
__ 19. Modify the Operator_Consoles and on Emergency_Operator_Consoles statement to add
terminal address 0040 to the front of the list of terminals.
__ 20. Add the following CP owned volumes: PAGE01, SPOOL1, and ALTRES. ALTRES should
be added at Slot 2 (after M01RES), SPOOL1 at Slot 15 (after M01S01), and PAGE01 at
Slot 254 (before M01P01 as the order for page is not relevant).
__ 21. Make the appropriate changes to set the timezone to display the correct time for the location
where the class is being taught.

V11.3
EXempty
__ 22. In the section “User volume for local minidisk,” add a statement “User_Volume_include”
and add all volumes that begin with 0X016, all volumes that begin with USER0 and all
volumes that begin with M01W0. These are volumes that should be attached to the system
at IPL time. Hint: Use the generic character * (asterisk).
__ 23. Code the Device statement so that real addresses 190 - 191 and 19D - 19E will be off line at
IPL time.
__ 24. Enable the facility to allow setting Privilege Classes (Hint: Features).
__ 25. Enable the facility to require System Shutdown Validation.
__ 26. Enable the facility to allow Auto_Warm_IPL startup of your system.
__ 27. Update the facility to allow for the use of VDISKs, with a maximum of 350000 blocks per
virtual machine.
__ 28. Add the appropriate statement that will define a VSWITCH named ZL00LAN2 that connects
to real addresses A010 and A013. See the instructions on Networking unit 5.
__ 29. Add or modify the statement to enable the RSCS Networking Product.
__ 30. File your changes.
__ 31. You made several changes to the system configuration file. Because we are new to this
process, we may have made some mistakes. Our friends in Endicott know this is possible,
so they provide a program that checks the syntax of the file that you just changed.
__ 32. The utility to check the SYSTEM CONFIG file syntax is on the 193 disk. Access this disk at
filemode T.
__ 33. Issue the command CPSYNTAX SYSTEM CONFIG Z. CPSYNTAX verifies the syntax only.
This is the message that you should receive:
vmlink maint 193
cpsyntax system config z
CONFIGURATION FILE PROCESSING COMPLETE -- NO ERRORS ENCOUNTERED.
Ready;
__ 34. If you encounter errors, return to the SYSTEM CONFIG file and correct them, then rerun the
CPSYNTAX program. When you have fixed all of your errors, continue with the next step.
Ask your instructor if you need assistance.
__ 35. When you have finished your modifications to the SYSTEM CONFIG file, detach the CF0
minidisk.
Part 5: Formatting and allocating CP volumes

__ 36. You have three DASD devices on your system that will be used for an alternate RES pack,
page, and spool space. You also have four DASD for minidisks for your Linux guest. These
devices are all labeled, but now we need to use the CPFMTXA program to format all seven
of them for CP usage.

V11.3
EXempty
First, we need to make these devices available to the MAINT virtual machine. Issue the
following commands:
ATTACH F00-F01 *
ATTACH 161-163 *
ATTACH 150 *
Previously in this lab you added three volumes to the CP_Owned list in the SYSTEM
CONFIG file. F00 will be formatted as PAGE01, F01 will be formatted as SPOOL1, and
150 will be formatted as ALTRES. We need to verify that MAINT has virtual devices at
address F00-F01 and 150. Issue these commands:
QUERY F00-F01
QUERY 150
QUERY VIRTUAL F00-F01
QUERY VIRTUAL 150
What is the status of these devices? ___________________________
__ 37. Enter CPFMTXA. You will have to run the program six times for F00, F01, 150, 161, 162, and
163. The following three steps provide the information that CPFMTXA will need in the
appropriate order to format and allocate the three DASD volumes for page, spool, and the
alternate RES pack.
__ 38. Here are the parameters you will have to pass to CPFMTXA for F00:
Select the FORMAT option.
Virtual Address - F00
Cylinder Range - 0 END
Volume Label - PAGE01
Do you want to continue? - YES
The allocation program will automatically start and then pause for input. Enter these
parameters:
PAGE 1 END
END
__ 39. Now run the program for F01.
Virtual Address - F01
Volume Label - SPOOL1
Do you want to continue - YES
Allocation parameters
SPOL 1 END
END

V11.3
EXempty
__ 40. Now run the program for 150.
Virtual Address - 150
Volume Label - ALTRES
Do you want to continue? - YES
Allocation parameters
PARM 1 END
END
__ 41. Now run the CPFMTXA program for 161-163. Format cylinders 0 to end, use a label format of
0X016n, and take the default allocation type for these volumes. Make sure that you have
not attached 160 and that you do not run CPFMTXA against 160. The 160 volume contains
a pre-installed Linux we will use later in the exercises.
__ 42. Next, run the CPFMTXA program for F00, F01, and 150. This time you will use the Owner
option and set it to NOSSI for the SSI owner and ZVMBxx for the system owner. Refer to
your student guide or see help for the syntax of this command.
Part 6: SALIPL EXEC

__ 43. Issue the SALIPL exec to change your SAPL screen.
Note: The first instance of “123” in the following SALIPL command refers to the virtual
device address (minidisk) of the SYSRES volume. This is a full pack mdisk on the M01RES
volume, which is defined on the starter system as MAINT’s 123 mdisk. The second instance
of “123” is the real address of the disk that contains the SYSTEM CONFIG file that is
delivered on VMCOM1. In our lab, VMCOM1 just happens to be DASD address 123, but
this does not refer to the same volume as MAINT's 123 minidisk.
salipl 123 (extent 1 comment ? iplparms pdvol=123 pdnum=1
When prompted enter up to four lines of comments or the SAPL screen.
Part 7: Testing your changes to the SYSTEM CONFIG

__ 44. Shut down your system and then IPL 125 with the loadparm option.
Did the system automatically perform a warm start? ________________
__ 45. Enter QUERY TIME. Is the time set properly? _________________________
__ 46. Issue the command QUERY ALLOC SPOOL. Do you see your new SPOOL volume?
_________________________
__ 47. Issue the command QUERY ALLOC PAGE. Do you see your new PAGE volume?
_________________________
Issue the command Query ALLOC ALL. This is another helpful system programming
command. What information does it provide?
_________________________________________________
_________________________________________________
_________________________________________________

V11.3
EXempty
__ 48. Issue the command INDICATE LOAD. What information does this provide? We will discuss
this command in a later topic.
_________________________________________________
_________________________________________________
_________________________________________________
Part 8: Backing up your changes to SYSTEM CONFIG on the back-up

PARM disk
(This is done when you are satisfied with the changes.)
__ 49. Disconnect from OPERATOR and log on to MAINT.
__ 50. Issue the command CPRELEASE A.
This will cause CP to release the CF1 PARM disk.
__ 51. Issue LINK * CF1 CF1 MR.
This allows MAINT to gain write access to the PARM disk (CF1).
__ 52. Issue ACCESS CF1 T.
__ 53. Issue LINK PMAINT CF0 CF0 RR, then ACCESS CF0 Z.
You now should have the CF1 and CF3 PARM disk in the CMS access order.
__ 54. Issue COPY SYSTEM CONFIG Z = = T (OLDDATE REPLACE.
This copies the updated system configuration file to the PARM disk.
__ 55. Issue the command to detach the CF0 and CF1 disks.
This releases the access of the PARM disks.
You might want to update the CF3 disk also but it is not necessary for the lab environment.
As an example, you can do the same steps above, where CF1 is linked R/O and accessed
as T; CF3 linked as MR (write) and accessed as Z. Then, you copy all files with the following
command to have the backup from CF1 to CF3:
COPY* * T = = Z (OLDD REP
Hint: This is a best practice to keep CF1 and CF3 in sync before you do any z/VM maintenance.
__ 56. Issue the command that will have the SYSTEM access the CF1 disk as A.
What command did you use? __________________________________.
__ 57. Shut down your system.
__ 58. Log off your user ZVMBnn virtual machine.
Congratulations, you have completed the lab!
End of exercise

V11.3
EXempty
Exercise solutions
Note: Examples are for student team ZVMB0T.
USER DIRECT File
USER DIRECT C1 F 80 Trunc=72 Size=4341 Line=122 Col=1 Alt=0
====>
USER $ALLOC$ NOLOG
MDISK A00 3390 000 001 VMCOM1 R
MDISK A02 3390 000 001 710RL1 R
MDISK A04 3390 000 001 M01RES R
MDISK A05 3390 000 001 M01W01 R
MDISK A06 3390 000 001 M01W02 R
MDISK A07 3390 000 001 M01W03 R
MDISK A08 3390 000 001 ALTRES R
MDISK A09 3390 000 001 PAGE01 R
MDISK A10 3390 000 001 SPOOL1 R
MDISK A12 3390 000 001 0X0161 R
MDISK A13 3390 000 001 0X0162 R
MDISK A14 3390 000 001 0X0163 R
*
***************************************************************
USER $EOD$ NOLOG
MDISK A00 3390 3337 01 M01W01 R
MDISK A01 3390 3337 01 M01W02 R
MDISK A02 3390 3337 01 M01W03 R
MDISK A04 3390 0049 01 PAGE01 R
MDISK A05 3390 0049 01 SPOOL1 R
MDISK A12 3390 03337 001 0X0161 R
MDISK A13 3390 03337 001 0X0162 R
MDISK A14 3390 00299 001 0X0163 R
***************************************************************

V11.3
EXempty
SYSTEM CONFIG file
SYSTEM CONFIG Z1 F 80 Trunc=80 Size=282 Line=25 Col=1 Alt=7
====>
/**********************************************************************/
/* CP_Owned Volume Statements */
/**********************************************************************/
-------------------- 25 line(s) not displayed --------------------
CP_Owned Slot 1 M01RES

CP_Owned Slot 2 ALTRES
CP_Owned Slot 5 VMCOM1
CP_Owned Slot 10 M01S01

CP_Owned Slot 15 SPOOL1
CP_Owned Slot 254 PAGE01

CP_Owned Slot 255 M01P01
. . .
/**********************************************************************/
/* User_Volume_List */
/**********************************************************************/
/* These volumes contain the minidisks for your guests, as well as */
/* the product disks for z/VM. Volumes that are not intended to hold */
/* "local" minidisks, i.e., minidisks that would be unique to a */
/* single system, should be kept on separate volumes. */

/**********************************************************************/
/* Shared Volume_List */
/**********************************************************************/
User_Volume_List 710RL1
/**********************************************************************/
/* User volumes for local minidisks */
/**********************************************************************/
User_Volume_Include USER0* 0X016* M01W0*

/**********************************************************************/
/**********************************************************************/
/* Status of Devices */

V11.3
EXempty
/**********************************************************************/
Devices ,
Online_at_IPL 0000-FFFF,
Offline_at_IPL 0190-0191 19D-19E,
Sensed 0000-FFFF
Features ,
Enable , /* Enable the following features */
Set_Privclass , /* Disallow SET PRIVCLASS command */
Auto_Warm_IPL , /* Prompt at IPL always */
Validate_Shutdown , /* Require SYSTEM parm */
Disable , /* Disable the following features */

Clear_TDisk , /* Don't clear TDisks at IPL time */
Retrieve , /* Retrieve options */
Default 20 , /* Default.... default is 20 */
Maximum 255 , /* Maximum.... default is 255 */
MaxUsers noLimit , /* No limit on number of users */
Passwords_on_Cmds , /* What commands allow passwords? */
Autolog yes , /* ... AUTOLOG does */
Link yes , /* ... LINK does */
log on yes, /* ... and log on does, too */
Vdisk Userlim 350000 blocks /* Maximum vdisk allowed per user */
/*********************************************************************/
Operator_Consoles 0040 0020 0021 0022 0023 0E20 0E21 1020 ,
System_3270 System_Console
Emergency_Message_Consoles 0020 0021 0022 0023 0E20 0E21 1020 ,
System_Console
. . .
Timezone_Definition EDT West 04.00.00
Timezone_Definition EST West 05.00.00
Timezone_Definition CDT West 05.00.00
Timezone_Definition CST West 06.00.00
Timezone_Definition MDT West 06.00.00
Timezone_Definition MST West 07.00.00
Timezone_Definition PDT West 07.00.00
Timezone_Definition PST West 08.00.00
Timezone_boundary on 2017-03-12 at 02:00:00 to EDT

Timezone_boundary on 2017-11-05 at 02:00:00 to EST



V11.3
EXempty


. . .
PRODUCT PRODID 7VMRSC10 STATE ENABLED DESCRIPTION '00/00/00.00:00:00.
$BASEDDR RSCS Networking'
PRODUCT PRODID 7VMDIR10 STATE DISABLED DESCRIPTION '00/00/00.00:00:00.$BASEDDR

DIRECTORY MAINTENANCE FACILITY (DirMaint)'
PRODUCT PRODID 7VMRAC10 STATE DISABLED DESCRIPTION '00/00/00.00:00:00.$BASEDDR

RACF Security Server'
PRODUCT PRODID 7VMPTK10 STATE DISABLED DESCRIPTION '00/00/00.00:00:00.$BASEDDR

PERFORMANCE TOOLKIT FOR VM'
. . .
/***************************************************************/
/* Guest LAN and VSwitch Definitions */
/*********************************************** ***************/
DEFINE VSWITCH ZL00LAN2 RDEV A010 A013 CONNECT CONTROLLER * VLAN 1

VMLAN MACPREFIX 02D021
* * * End of File * * *

V11.3
EXempty
QUERY ALLOCATE commands
q alloc page
EXTENT EXTENT TOTAL PAGES HIGH %
VOLID RDEV START END PAGES IN USE PAGE USED
------ ---- ---------- ---------- ------ ------ ------ ----
PAGE01 0F00 1 49 8820 5084 5845 57%
M01P01 0129 1 3337 600660 5110 5897 1%
------ ------ ----
SUMMARY 609480 10194 1%
USABLE 609480 10194 1%
Ready; T=0.01/0.01 10:01:50
q alloc spool
EXTENT EXTENT TOTAL PAGES HIGH %
VOLID RDEV START END PAGES IN USE PAGE USED
------ ---- ---------- ---------- ------ ------ ------ ----
M01S01 0128 1 3337 600660 11289 31680 1%
SPOOL1 0F01 1 49 8820 8816 8816 99%
------ ------ ----
SUMMARY 609480 20105 3%
USABLE 609480 20105 3%
Ready; T=0.01/0.01 10:03:15
DASD 0127 M01RES 3390 CKD-ECKD (UNITS IN CYLINDERS)
TDISK TOTAL=00000000000 INUSE=00000000000 AVAIL=00000000000
PAGE TOTAL=00000000000 INUSE=00000000000 AVAIL=00000000000
SPOOL TOTAL=00000000000 INUSE=00000000000 AVAIL=00000000000
DRCT TOTAL=00000000020 INUSE=00000000001 AVAIL=00000000019, ACTIVE
DASD 0150 ALTRES 3390 CKD-ECKD (UNITS IN CYLINDERS)
DRCT TOTAL=00000000000 INUSE=00000000000 AVAIL=00000000000
DASD 0124 VMCOM1 3390 CKD-ECKD (UNITS IN CYLINDERS)
DASD 0128 M01S01 3390 CKD-ECKD (UNITS IN CYLINDERS)
DASD 0F01 SPOOL1 3390 CKD-ECKD (UNITS IN CYLINDERS)
DASD 0F00 PAGE01 3390 CKD-ECKD (UNITS IN CYLINDERS)

V11.3
EXempty
DASD 0129 M01P01 3390 CKD-ECKD (UNITS IN CYLINDERS)
IPL NUCLEUS ACTIVE ON VOLUME M01RES
Ready; T=0.01/0.01 21:42:05
ind load
AVGPROC-000% 01
MDC READS-000001/SEC WRITES-000000/SEC HIT RATIO-072%
PAGING-0/SEC STEAL-000%
Q0-00000(00000) DORMANT-00011
Q1-00000(00000) E1-00000(00000)
Q2-00000(00000) EXPAN-001 E2-00000(00000)
Q3-00000(00000) EXPAN-001 E3-00000(00000)
PROC 0000-000% CP
LIMITED-00000
Ready; T=0.01/0.01 21:43:04

V11.3
Exercise 4. z/VM User Directory
EXempty
Estimated time
02:30
Overview
In this exercise, the students will add one CMS virtual machine and one Linux
guest virtual machine to their system directory.
Objectives
• Run the DISKMAP exec
• Add virtual machines to the USER DIRECT file
• Put the directory online
Requirements

going to perform.

Part 1: Log on and start up your z/VM guest system
__ 1. Log on to your first-level virtual machine.
__ 2. Set up and IPL your z/VM system.
__ a. Enter SYSTEM RESET.
__ b. Enter TERM CONMODE 3270.
__ c. Enter IPL 125 CLEAR LOADPARM 020. This will display the SAPL screen. Add
CONS=020 as an IPL parameter in the middle of the screen and press F10.
__ d. Perform a warm start. If a warm start does not work, use force.
__ e. When prompted to change the time of day clock press Enter.
__ 3. When the screen goes into HOLDING or MORE... clear the screen. Continue to do this until
the IPL process completes.
__ 4. Disconnect from the SYSTEM OPERATOR.
__ 5. You should see the system logo for the z/VM system. Log on from this screen as userid
MAINT; use the surrogate id IBMVM1. Press the Enter key after you log on to bypass the
VM READ status.
__ 6. Verify that you are logged on to the MAINT virtual machine.
What command could you use? _____________ or ________________
Part 2: Locating the system directory file

__ 7. Issue the QUERY DASD ALL command. This shows you all of the DASD that is available to
your second-level z/VM 7.1 system. (These are actually mdisks on your ZVMBnn virtual
machine.)
__ 8. Enter filelist user direct *.
Note: Instead of spelling out filelist, you could use the synonym that was created in the last
exercise in the SYN SYNONYM file.
__ 9. This will show you all the files that exist on your system with this filename and filetype. You
should have only one, on the C disk.
__ 10. XEDIT this file. You can enter X in the CMD area of this file, or you can move your cursor to
this file and press PF11.
__ 11. Edit the USER DIRECT file on mdisk 2CC. Add more mdisk entries for $ALLOC$ to protect
cylinder zero of the following four volumes that will be added in this exercise: 0X0161,
0X0162, M01W01, M01W02, M01W03.
__ 12. In the lecture, we discussed a placeholder virtual machine called $EOD$. Let’s add that one
now.
__ 13. To create this ID, you may replicate one of the other place holder IDs. Then, create a mdisk
at cylinder 10015 for a length of 1 for volume M01RES.

V11.3
EXempty
__ 14. Add entries for $EOD$ to indicate,
▪ The last cylinder of 0X0161, 0x0162, M01W01, M01W02, M01W03 starting with cylinder
3337 for a length of one cylinder.
▪ For volume 0x0163 starting at cylinder 299 for a length of one cylinder.
__ 15. This would be a good time to change the default password for users that are shipped with
the system (that is, MAINT, PMAINT, and so on). Use the appropriate LOCATE command to
determine what the default password is. Then, use the XEDIT CHANGE command to change
ALL occurrences of the default password to ZL00.
Part 3: Running the Diskmap exec

__ 16. Enter DISKMAP USER DIRECT.
__ 17. XEDIT the file that was created on your A disk by the diskmap exec.
What file was created on your “A” disk? _____________ ______________
Examine this file to see how it is organized.
__ 18. Use the ALL XEDIT command to locate all occurrences of the word OVERLAP.
Did you find any? _______________
It is always a good idea to check for overlaps before you make any changes to the USER
DIRECT file.
__ 19. Issue the XEDIT command to LOCATE any occurrence of the word GAP on the M01RES
volume.
What cylinders are available on the M01W01 volume?
Starting cyl: __________ Ending cyl: _________ No. of cyls: __________
__ 20. We will need the preceding information shortly, but for now close this file.
Part 4: Adding users to the USER DIRECT file

Scenario: You are responsible for directory maintenance at your location. To do this, you perform
the following tasks:
• XEDIT the USER DIRECT file.
• Add two new users, one a single configuration and the other a multi-configuration virtual
machine.
• Check DISKMAP again to see whether you have created an overlap (very important).
• Place the updated directory on line.
• Test your new userids.

Below you see two Directory Maintenance Requests that have been submitted to you. Read
through them, but do not do anything with them at this time. Continue with step 21.
DIRECTORY MAINTENANCE REQUEST

USERID: userid PASSWORD: XXXXX Configuration: Single _____ Multi __X___
DISK SPACE: 2 cylinders (Virtual 191)
STORAGE REQUIREMENTS: 32M at log on , 64M Max
Single-system CMS USER (Y/N): Y (IPL CMS)
ADDITIONAL REQUIREMENTS: Machine XC

Need an automatic IPL of CMS, and the usual console, printer, punch and reader, and
the standard links for a CMS virtual machine.
DIRECTORY MAINTENANCE REQUEST

USERID: LINUX1 PASSWORD: XXXXX Configuration: Single __X__ Multi _____
DISK SPACE: 1000 cylinder (Virtual 191)
STORAGE REQUIREMENTS: 512M at log on , 1G Max
Single-system CMS USER (Y/N): Y (IPL CMS)
ADDITIONAL REQUIREMENTS: Machine ESA

Need an automatic IPL of CMS, and the usual console, printer, punch and reader, and
the standard links for a CMS virtual machine.
__ 21. XEDIT the USER DIRECT file. Add additional mdisk entries for $ALLOC$ to protect
cylinder zero of the following three volumes, which you add in a later exercise: ALTRES,
PAGE01, and SPOOL1 volumes.
__ 22. Add an entry for $EOD$ to protect,
▪ The last cylinder of ALTRES starting with cylinder 64 for a length of one cylinder.
▪ Cylinder 10015 for a length of one cylinder on PAGE01 and SPOOL1.
__ 23. Create a PROFILE statement called LNXDFLT.
__ a. Add an IPL statement for the CMS saved system.
__ b. Add a MACHINE ESA statement with 8 virtual CPUs.
__ c. Add CPU statements to have 2 virtual CPUs at logon and define CPU 0 as the base
CPU.
__ d. Add a CONSOLE and the three SPOOL statements that are required for CMS users.

V11.3
EXempty
__ e. Add the LINKs for MAINT's 190, 19D, and 19E, 490 minidisks for CMS access.
Note: Technically, MAINT does not own a 490 disk. Its 490 disk is actually a link to
MAINT710’s 490 disk, but it is allowed to have a link to another link.
__ f. Add the LINKs to tcpmaint 592 minidisk.
__ g. Grant access to vswitch ZL00LAN2 to userid.
__ h. Create a virtual NIC 1000.
__ i. Couple the NIC to vswitch ZL00LAN2.
__ 24. Using the first Directory Maintenance Request from the previous page, along with the
following information, add a directory entry for the userid virtual machine. This is a userid of
your choice. This will be a Multi-configuration virtual machine.
__ a. Define this userid to be a superuser with privilege class A through G.
__ b. Include the PROFILE you just created.
__ c. Add an IPL statement that will override the IPL in the PROFILE. It will automatically
bypass the VM READ (Hint: PARM parameter).
__ d. Userid virtual machine runs in an XC (you will have to override the profile) architected
machine.
__ e. Add the OPTION to link to mdisk of other virtual machines without a password (Hint:
Options).
__ f. Add a 191 disk, by using information from the DISKMAP. This disk should be on
M01RES.
__ g. Define a LINK statement to the virtual machine MAINT710’s address 201 as userid’s
virtual 201.
__ 25. Using the second Directory Maintenance Request from the previous page, along with the
following information, add a directory entry for the LINUX1 virtual machine.
__ a. Define this virtual machine to have CLASS BEG.
__ b. Include the PROFILE that was previously created.
__ c. LINUX1 virtual machine runs in an ESA-architected machine.
__ d. Add an IPL statement that will override the IPL in the PROFILE. It will automatically
bypass the VM READ.
__ e. Define the user's 191 disk, by using information from the DISKMAP. This disk should be
on M01W01.
__ f. Add 100 and 101 disk for the user on volume 0x0161 and 0x0162.
__ 26. Add a directory entry RHEL by using the following statement. This virtual machine will be
used in later labs.
USER RHEL Zl00 1G 2G BEG
INCLUDE LNXDFLT
COMMAND DEFINE STORAGE 1G STANDBY 1G
IPL 150

__ 27. Locate the directory entry for the system OPERATOR, and add an IPL statement that will
bypass VM READ when the OPERATOR logs on.
__ 28. Add the OPTION that allows OPERATOR to link to other virtual machines mdisks without a
password.
__ 29. File your changes.
__ 30. Run the DISKMAP again and then verify that no OVERLAPS were created as a result of
adding these minidisks to the virtual machines.
Part 5: Putting the updated directory online

__ 31. Enter the following command:
DIRECTXA USER DIRECT
__ 32. Read the message closely. You are looking for a message that looks like the following
example.
directxa user direct

z/VM USER DIRECTORY CREATION PROGRAM - VERSION 6 RELEASE 3.0
EOJ DIRECTORY UPDATED AND ON LINE
HCPDIR494I User directory occupies 58 disk pages
Did you see the EOJ Directory Updated and On Line message?
____________________________
Part 6: Testing your new virtual machines

__ 33. From the MAINT virtual machine, issue the DISCONNECT command.
__ 34. The system logo should now be displayed. Log on to your LINUX1 guest system and make
sure that it logs on, IPL’s CMS, and bypasses the VM READ.
Note: Disregard the message about the VSWITCH not existing. You address this issue in a
later exercise.
Also, you should see a message about a device error for the 191 disk. This is because the
disk is not available for use by CMS. The disk must be formatted. You will address this issue
now.
__ 35. First, make sure that you are logged on to LINUX1, and not on the MAINT virtual machine.
When you are sure that you are logged on to the correct virtual machine, enter HELP
FORMAT from the command line of your CMS session. Then, issue the FORMAT command to
format the 191 disk with filemode A. When prompted, specify any appropriate disk label.
After the format command completes, issue the Query Disk command to verify the 191
has been accessed as A.
__ 36. Using XEDIT create a PROFILE EXEC on the A disk for LINUX1 with the following lines:
/* Profile Exec */
'set pf12 retrieve'

V11.3
EXempty
'set run on'
__ 37. Execute the PROFILE EXEC that you just created (type PROFILE at the command line) to
verify that there are no errors. Log off from LINUX1.
__ 38. Perform these same tasks for the userid virtual machine, but for this PROFILE EXEC
include the following commands:
/* Profile Exec */
'set pf12 retrieve'
'set run on'
'access 201 z'
__ 39. Execute your PROFILE EXEC and issue the QUERY DISK command to verify that your
profile worked successfully.
Do you see the 201 disk accessed as filemode Z? ______________
__ 40. Issue the SHUTDOWN command from the userid virtual machine (to verify that you gave
userid the class A privilege class). Then, log off from your ZVMBnn team virtual machine.
Congratulations, you have completed the lab.
End of exercise

Exercise solutions
USER DISKMAP A
VOLUME USERID CUU DEVTYPE START END SIZE

M01RES $ALLOC$ A05 3390 00000 00000 00001
VMSERVS 305 3390 00001 00167 00167
VSMWORK3 191 3390 00168 00192 00025
VSMREQIN 191 3390 00193 00217 00025
.
.
.
CBDIODSP 191 3390 05377 05496 00120

CBDIODSP 400 3390 05497 06216 00360
$EOD$ A00 3390 10015 10016 00001
USER DIRECT C
PROFILE LNXDFTL
COMMAND SET VSWITCH ZL00LAN2 GRANT &USERID
COMMAND DEFINE NIC 1000 QDIO
COMMAND COUPLE 1000 TO SYSTEM ZL00LAN2
IPL CMS
MACH ESA 8
CPU 00 BASE
CPU 01
SPOOL 000C 2540 READER *
SPOOL 000D 2540 PUNCH A
SPOOL 000E 1403 A
CONSOLE 009 3215 T
LINK MAINT 0190 0190 RR
LINK MAINT 019D 019D RR
LINK MAINT 019E 019E RR
LINK MAINT 0490 0490 RR
LINK TCPMAINT 0592 0592 RR
*
**************************
USER $ALLOC$ NOLOG

MDISK A00 3390 000 001 VMCOM1 R
MDISK A01 3390 000 001 VMCOM2 R
MDISK A02 3390 000 001 710RL1 R

V11.3
EXempty
MDISK A04 3390 000 001 M01RES R
MDISK A05 3390 000 001 0x0161 R

MDISK A06 3390 000 001 0x0162 R
MDISK A07 3390 000 001 M01W01 R
MDISK A08 3390 000 001 M01W02 R
MDISK A06 3390 000 001 M01W03 R
MDISK A09 3390 000 001 SPOOL1 R
MDISK A10 3390 000 001 PAGE01 R
*
*********************************
*
USER $EOD$ NOLOG
MDISK A00 3390 10015 001 M01RES R
MDISK A01 3390 3337 001 0x0161 R
MDISK A02 3390 3337 001 0x0162 R
MDISK A03 3390 299 001 0x0163 R
MDISK A04 3390 3337 001 M01W01 R
MDISK A05 3390 3337 001 M01W02 R
MDISK A06 3390 3337 001 M01W03 R
MDISK A08 3390 10015 001 SPOOL1 R
MDISK A09 3390 10015 001 PAGE01 R
*
*********************************
*
IDENTITY userid password 32M 64M ABCDEFG
INCLUDE LNXDLFLT
BUILD ON SSI1 USING SUBCONFIG SSI-1
OPTION LNKNOPAS
IPL CMS PARM AUTOCR
MACH XC
SUBCONFIG SSI-1
MDISK 191 3390 6218 002 M01RES MR READ WRITE MULTI
LINK MAINT710 201 201 RR
*
****************************
*
USER LINUX1 Zl00 512M 1G BEG
INCLUDE LNXDFLT
IPL CMS PARM AUTOCR
MDISK 0191 3390 1 END M01W01 MR read write multi
MDISK 0100 3390 1 end 0x0160 MR read write multi
MDISK 0101 3390 1 end 0x0161 MR read write multi
NICDEF B000 TYPE QDIO DEVICES 3 LAN SYSTEM ZL00LAN2 MACID 600001
*

DENTITY OPERATOR ZL00 32M 32M ABCDEFG

INCLUDE IBMDFLT
BUILD ON * USING SUBCONFIG OPERTR-1
AUTOLOG AUTOLOG1 OP1 MAINT

ACCOUNT 2 OPERATOR
MACH ESA
OPTION MAINTCCW LNKNOPAS
IPL CMS PARM AUTOCR
SUBCONFIG OPERTR-1
LINK OP1 191 192 RR
MDISK 191 3390 2924 005 M01RES MR READ WRITE MULTIPLE

V11.3
Exercise 5. z/VM networking
EXempty
Estimated time
01:30
Overview
In this exercise, the student is required to configure the appropriate files to run
TCP/IP on their system. They will also automate the startup of TCP/IP services at
system IPL time.
Objectives
• Automate the startup of TCP/IP services
• Update the system directory for TCP/IP
• Modify the DTCPARMS file
• Modify the TCPIP DATA file
• Modify the PROFILE TCPIP file
• Test the TCP/IP services with PING and TELNET
Requirements
• TCP/IP Planning and Customization Guide

going to perform.
Instructor Note: Perform a demo on how to modify the parameters for PCOMM before the lab
starts.

V11.3
EXempty
Part 1: Log on and start up your z/VM guest system
__ 1. Log on to your team virtual machine.
__ 2. Set up and IPL your guest z/VM system.
__ 3. Disconnect from OPERATOR and log on to the MAINT virtual machine.
Part 2: Directory modifications for TCPIP

__ 4. Edit the USER DIRECT file. (PMAINT 2CC disk)
__ 5. Locate the user TCPMAINT, and confirm if password is LBYONLY. It means that you need
to surrogate to TCPMAINT user ID using IBMVM1.
Note: On a z/VM SSI cluster, the TCPMAINT is an IDENTITY.
__ 6. Locate the user AUTOLOG1, and determine what the MULT password is for the 191 mdisk.
You will need this information in a later step. ___________________
Note: On a z/VM SSI cluster, the AUTOLOG1 uses SUBCONFIGs.
__ 7. Locate the entry PROFILE TCPCMSU. You need to make a change to the CONSOLE
statement. Add TCPMAINT to the end of that line. This enables the Secondary Console
Image Facility (SCIF) for all of the TCPIP service machines. It should look like this:
CONSOLE 009 3215 T TCPMAINT
__ 8. File your changes to the USER DIRECT file.
__ 9. Place the directory on line.
What command did you use to perform this task? __________________________
__ 10. Log off from MAINT.
__ 11. Refer to the table on the next page for the following steps.

V11.3
EXempty
z/VM TCPIP stack hostname table
Team OSA device address Hostname IP address
ZVMB21 A000, A001, A002 zvmb21.ilsvpn.ibm.com 10.31.184.104
Part 3: Tailoring TCPIP, using IPWIZARD

__ 12. For this lab exercise, you use Chapter 9 of the z/VM Installation Guide on the student CD as
your guide. Start with Step 1. “Configure TCP/IP for an initial network connection” (page 91).
__ 13. Find your TCPIP Configuration Worksheet in the Appendix of this exercise guide and
complete the worksheet with the information provided here:
Host Name (from the preceding Hostname table)
Domain Name - ILSVPN.IBM.COM
Gateway IP Address - 10.31.188.1
DNS Address - 10.31.160.2 and 10.31.160.3
Interface Name - whatever you wish to name your OSA link.
Device number - A000
IP Address - (from the Hostname table)
Subnet Mask - 255.255.248.0
Interface Type - QDIO Layer 3
__ 14. Complete substeps 1 - 7 of Step 1 using the worksheet and the additional information
provided here:
Router type - None
MTU = 1500
__ 15. Answer Yes (1) to the question about restarting the TCPIP stack virtual machine.

V11.3
EXempty
__ 16. If you did not receive a message about the IPWIZARD completing successfully, have the
IPWIZARD tool try to ping the connections again. If you still have problems, verify that all
the parameters are correct. Contact your instructor if you need assistance.
Note: The ping from IPWIZARD can fail. Continue finishing IPWIZARD without changing
information; ping default gateway after IPWIZARD completes.
__ 17. Log off from the MAINT710 virtual machine.
Part 4: Logging on to TCPMAINT

__ 18. Log on to the TCPMAINT virtual machine (Using the surrogate ID called IBMVM1).
When you configure TCP/IP services, you view or edit files on the 198, 591, and 592 disks.
You need to verify that these disks are accessed. What command can you use to show what
disks have been accessed by CMS, for the virtual machine TCPMAINT?
___________________________________________
What do you think caused these disks to be accessed when we logged on and IPLed CMS?
_______________________________________________________
__ 19. Modify the PROFILE EXEC file and add the following commands. Replace the “nn” in the
first command with the PF key number of your choice. Put these commands in between
quotation marks (' ') so that they are treated as literal strings by REXX. (You can use either
single or double quotes.) Also, if you add these lines after the ‘ADDRESS COMMAND’
instruction, be sure to type the commands in UPPER case.
‘CP SET PFnn RETRIEVE FORWARD’
‘CP SET RUN ON’
When you are done, see whether you can find any commands that cause mdisk to be
accessed.
__ 20. Save this file when you have finished.
__ 21. Execute your new PROFILE EXEC. You can either enter IPL CMS or type PROFILE on the
command line, and press Enter to perform this task.
__ 22. Issue the QUERY DISK command to verify that your profile accessed the disks as directed.
Now, it is time to start tailoring the TCP/IP features.
Part 5: Tailoring the DTCPARMS file

__ 23. Enter the following command: filel * dtcparms *
You should see two files:
- SYSTEM DTCPARMS (This was created by the IPWIZARD exec.)
- IBM DTCPARMS (Never change this file.)
__ 24. The file that you modify is the SYSTEM DTCPARMS file. This file will need to be tailored for
our lab system.

V11.3
EXempty
__ 25. Edit the SYSTEM DTCPARMS file and add the required information to define a virtual NIC to
the TCPIP server at address D000-D002 connecting to the SYSTEM VSWITCH named
ZL00LAN2. The A000 address (that is already there) was added as a real network
connection by the IPWIZARD. This new adapter will be used as a connection to a
VSWITCH on your system, as an additional network connection.
Syntax: :vnic.<VIRTUAL_ADDRESS> SYSTEM <VSWITCH_NAME>
Note: To couple TCPIP to VSWITCH, you do not need to attach the devices using
the nic tag. Ensure that they appear on the vnic tag.
__ 26. Add an entry for the FTP server. This entry is not required, but is a good idea for
documentation.
:nick.FTPSERVE :type.server
:class.ftp
:anonymous.no
__ 27. Save your changes to the file, and close the XEDIT session. Exit from the filelist display and
return to CMS.
__ 28. Issue the command to grant TCIP access to the vswitch ZL00LAN2.
__ 29. Don’t forget to update the SYSTEM CONFIG file with MODIFY VSWITCH ZL00LAN2
GRANT TCPIP statement (refer to Lab 3 for SYSTEM CONFIG).
Part 6: Tailoring the TCPIP DATA file

__ 30. Execute the filelist command to display a list of all files that have a filename of TCPIP.
You will notice that there are several. We are interested in the file that has a filetype of
DATA. Notice there is also a file with a filetype of SDATA. This is the sample or backup file.
__ 31. XEDIT the TCPIP DATA file.
__ 32. We do not need to change any statements in this file, as they were modified by the
IPWIZARD exec. Just verify this information:
▪ HOSTNAME ZVMBnn (where nn is your team number)
▪ DOMAINORIGIN ILSVPN.IBM.COM
▪ NSINTERADDR 10.31.160.2 and 10.31.160.3
Accept the defaults for the rest of the file.
__ 33. Save your changes (if any were made) and exit from this file.
Part 7: Tailoring the PROFILE TCPIP file

__ 34. Enter the command that shows you a list of all the files that have a filename of PROFILE.
We are looking for the two files that have TCPIP in the filetype. When you use the
IPWIZARD exec to configure TCPIP, it takes the default Free Pool values. Some of these
need to be changed. You can type these into the file, or you can cut and paste the lines from
the file PROFILE STCPIP. This is the sample PROFILE TCPIP file (it contains all the
possible definitions that might need to be added).

V11.3
EXempty
These statements must be the first non-commented statements in the file, and they must
follow the lines that look like this:
; %%File Origin Indicator - DO NOT REMOVE OR ALTER the next line%%
; %%TCPIP%%PROFILE%%STCPIP%%
__ 35. Add all the Free Pool Statements that are in the sample file to PROFILE TCPIP. in the
beginning of the file. When you have finished adding the Free Pool Statements to
PROFILE TCPIP, update these four statements (take the defaults for all other statements).
ACBPOOLSIZE 2500
SMALLDATABUFFERPOOLSIZE 500
TINYDATABUFFERPOOLSIZE 200
UCBPOOLSIZE 2500 .
__ 36. Add the following statements to the PROFILE TCPIP.
(For any tags that you add, make sure that they have their corresponding end tag when
required. You may want to check samples available in PROFILE STCPIP file that is located
on TCPMAINT 592 disk)
- MONITORRECORDS (This will produce detailed information about TCPIP, for use with
VM Performance Toolkit.)
- SYSCONTACT (Your name and any phone number.)
- AUTOLOG FTPSERVE.
Also, remember to enable the ports for FTP.
__ 37. Add a Device and Link statement to define the connection to D000-D002. This will be an IP
transport link statement, QDIO Layer 3 (this is the connection to the VNIC you defined in
your SYSTEM DTCPARMS file).
__ 38. Add a Home statement for a device at address 192.168.1.nnn (where nnn is the same as
the last octet in your other home statement. (ZVMB21 would use 104, ZVMB22 would use
106, and so on). This is the address of your system on the alternate network. Use a subnet
mask of 255.255.255.0.
__ 39. Add a Start statement for your new device.
__ 40. Save your changes and exit from this file.
Part 8: Automating the startup of the TCP/IP virtual machine

__ 41. You need to update the PROFILE EXEC file on the virtual machine AUTOLOG1. To do this,
you have a couple of options. You could log on to AUTOLOG1, or you can link to
AUTOLOG1's 191 disk in write mode and make the changes from this virtual machine
(TCPMAINT). Use the second method, so you don’t have to log off of TCPMAINT and then
log on to AUTOLOG1.
__ 42. Issue the following commands:
link autolog1 191 fff mr
access fff z
__ 43. Enter the command to display all the files on AUTOLOG1's 191 disk. You should see
AUTOLOG1's PROFILE EXEC file on the Z disk.

V11.3
EXempty
__ 44. Edit this file. Add a PIPE CP XAUTOLOG statement to this file for the userid TCPIP before
the DTCVSW1 and DTCVSW2 virtual machines. (This will allow AUTOLOG1 to
automatically start the TCPIP virtual machine at system startup.)
__ 45. File your changes to this file, and exit from the filelist display. Detach the Z disk.
Part 9: Starting the TCP/IP virtual machine

When you ran the IPWIZARD exec, the last question that you were asked was whether you wanted
to restart the TCP/IP stack machine. If you answered YES to this question, TCPIP is currently
logged on, but has not seen any of the changes that you have made.
__ 46. Issue the (Class A) CP command force tcpip.
__ 47. Issue the QUERY TCPIP command, and verify that TCPIP is not logged on.
__ 48. Issue the (Class A) CP command XAUTOLOG AUTOLOG1.
__ 49. You should watch for the following statement. (Don’t be alarmed if you miss this message.)
DTCIPI023I TCP-IP initialization complete
__ 50. After the screen stops filling up, issue the QUERY NAMES command. Do you see the TCPIP
virtual machines listed? If so, what is their status?
_ TCPIP __________
_ FTPSERVE ________
__ 51. Issue the command NETSTAT DEVLINK. Do you see a status of Ready for both of your
OSA devices? ________________________________
__ 52. Issue the command NETSTAT HOME. Do you see both home addresses for your system?
___________________________________________
If you received the two IP addresses of your ZVMBnn system, you were successful in
getting TCP/IP started. If not, contact your instructor for help in debugging the problem with
your TCP/IP configuration.
__ 53. Issue the command NETSTAT GATE. Do you see your default gateway and both subnets?
___________________________________________
__ 54. Issue the command NETSTAT POOL. Are all allocations set according to what you
specified? ___________________________________________
__ 55. Issue the QUERY LAN DETAILS command. Do you see that TCPIP is connected to the
virtual switch (under Adapter Connections)? __________________________
Part 10: Testing the TCP/IP configuration

__ 56. Use the ping command to ping your system.
PING 10.31.184.nnn (Use the address from the NETSTAT HOME command.)
Did you receive any data back from the ping command? ____________
__ 57. Ping the 192.168.1.nnn address of your TCPIP connection. Where you successful?
______________

V11.3
EXempty
__ 58. Ping the IP address (10.31.184.nnn) of some of the other teams to see whether they
have successfully configured their TCPIP environment. You might need to ask other teams
to find out who has their TCPIP connection up and running. Were you successful?
_____________
__ 59. Verify that your system is actually on the IBM Education Network. Use the PCOMM
application on your workstation desktop to TELNET to your system, and log on as MAINT.
You will have to tailor the PCOMM application to connect to your host system’s
10.31.184.nnn address. The instructor will show you how to configure the TELNET session
if you have difficulty. Each location has different levels of the PCOMM application, and it
would not be possible to document this in the student exercise guide.
Instructor note: Perform a demo on how to modify the parameters for PCOMM before the
lab starts.
Were you able to TELNET to your host system? ___________________________
If not, get assistance from your instructor to troubleshoot the problem.
__ 60. From your classroom desktop, select Windows Start, then Run, and enter cmd.
__ 61. Use your desktop cmd window to FTP to your 10.31.184.nnn IP address.
__ 62. Authenticate as LINUX1. (The same password is used for FTP and LINUX1 z/VM logon.)
__ 63. Were you successful? __________ If not, determine why your FTP server is not working.
Ask for assistance from your instructor if needed.
Note: You have completed the FTP tests if you write quit to leave the FTP session.
__ 64. From your TCPMAINT session, copy the PROFILE TCPIP, TCPIP DATA, and SYSTEM
DTCPARMS files to TCPMAINT’s 191 disk with a filetype of BACKUP.
Where you successful? ____________________________
__ 65. From your PCOMM session (MAINT) shutdown your system. Where do the shutdown
messages show up? __________________________
__ 66. Are you still able to issue commands from MAINT’s PCOMM session? _______
__ 67. Save your PCOMM session. (From the drop-down, select File, then Save). Use any name
that you like.
__ 68. Close MAINT’s PCOMM session.
__ 69. Log off your team virtual machine when the shutdown completes.
Congratulations, you have successfully completed the lab exercise.
End of exercise

V11.3
EXempty
Exercise solutions
Note: Examples are for student team ZVMB2T.
USER DIRECT file
. . .
00065 PROFILE TCPCMSU
00066 IPL CMS
00067 MACH ESA
00068 SPOOL 000C 2540 READER *
00069 SPOOL 000D 2540 PUNCH A
00070 SPOOL 000E 1403 A
00071 CONSOLE 009 3215 T TCPMAINT
00072 LINK MAINT 0190 0190 RR
00073 LINK MAINT 019D 019D RR
00074 LINK MAINT 019E 019E RR
00075 LINK MAINT 0402 0402 RR
00076 LINK MAINT 0401 0401 RR
. . .
01964 IDENTITY TCPIP TCPIP 128M 256M ABG
01965 INCLUDE TCPCMSU
01966 BUILD ON SSI1 USING SUBCONFIG TCPIP-1
01967 * BUILD ON @@member2name USING SUBCONFIG TCPIP-2
01970 OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 APPLMON
01971 SHARE RELATIVE 3000
01972 IUCV ALLOW
01973 IUCV ANY PRIORITY
01974 IUCV *CCS PRIORITY MSGLIMIT 255
01975 IUCV *VSWITCH MSGLIMIT 65535
01976 NICDEF D00 TYPE QDIO LAN SYSTEM SWITCH60 MACID 800200
. . .
02009 IDENTITY TCPMAINT TCPMAINT 32M 64M ABCG
02010 INCLUDE TCPCMSU
02011 BUILD ON SSI1 USING SUBCONFIG TCPMNT-1
. . .

V11.3
EXempty
PROFILE EXEC A (for TCPMAINT)
00000 * * * Top of File * * *
00001 /* PROFILE EXEC */
00002 /*=====================================================================*/
00003 /* PROFILE EXEC for TCPMAINT server virtual machine. */
00004 /* */
00005 /* This file is provided as a "minimalist" PROFILE EXEC for the */
00006 /* TCPMAINT user ID (or its equivalent). */
00007 /*---------------------------------------------------------------------*/
00008 /* This profile can (and should) be modified to meet any specific */
00009 /* requirements for your installation. */
00010 /* */
00011 /* Note: It is strongly recommended that the TCPMAINT user ID (or its */
00012 /* equivalent) always access the resources identified in the */
00013 /* "TCP/IP MINIDISKS" section at the end of this sample. */
00014 /*=====================================================================*/
00015 Address 'COMMAND'
00016 rc = 0
00017 Use_SFS? = '0' /* SFS environment? (Boolean) */
00018 _mhdr = "Profile..:" /* Profile message header */
00019 _ehdr = "Profile-->" /* Profile err. message header */
00020 /*=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-*/
00021 /* Set terminal mode to 'VM' so attentions are reflected to CMS, and */
00022 /* not to CP. This must be set prior to issuance of -any- other CP or */
00023 /* CMS commands. Doing so prevents TCPMAINT from assuming the role of */
00024 /* primary system operator (SYSOPER) in the event it is the first */
00025 /* Class A virtual machine to be logged on. */
00026 /*=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-*/
00027 'CP TERM MODE VM'
00028
00029 /*---------------------------------------------------------------------*/
00030 /* Set up PF Key(s) and report settings. */
00031 /*---------------------------------------------------------------------*/
00032 Say _mhdr "Spooling console to self ("Userid()")..."
00033 'CP SPOOL CONSOLE * START'
00034 Say _mhdr "Setting PF Keys..."
00035 'CP SET PF11 RETRIEVE FORWARD'
00036 'CP SET PF12 RETRIEVE BACKWARD 1'
00037 'CP SET RUN ON'
00038 'PIPE' '(Name Report_PF_Settings)' ,
00039 'CP QUERY PF' ,
00040 '| Nlocate W2 /UNDEFINED/' ,
00041 '| Cons '
00042
00043 /*---------------------------------------------------------------------*/
00044 /* Account for minidisk or SFS environment differences. */
00045 /*---------------------------------------------------------------------*/
00046 If (Use_SFS?)

V11.3
EXempty
00047 Then Do
00048 Say _mhdr "Setting SFS environment workspace..."
00049 fpool_id = 'VMSYS:' /* Identify file pool */
00050 'SET FILEPOOL' fpool_id /* Set default file pool */
00051 workspace = '.' /* Use "top" directory */
00052 End
00053 Else Do
00054 Say _mhdr "Setting minidisk environment workspace..."
00055 workspace = '191' /* Use 191 minidisk */
00056 End
00057
00058 /*---------------------------------------------------------------------*/
00059 /* Access user work space. */
00060 /*---------------------------------------------------------------------*/
00061 'ACCESS' workspace 'A' /* Access user "A-mode" workspace */
00062
00063 /*---------------------------------------------------------------------*/
00064 /* TCP/IP Minidisk Setup */
00065 /*---------------------------------------------------------------------*/
00066 /* Access minidisks required for managing/using TCP/IP services. */
00067 /*---------------------------------------------------------------------*/
00068 'ACCESS' '198' 'D' /* Access configuration files disk */
00069 'ACCESS' '591' 'E' /* Access the server modules disk */
00070 'ACCESS' '592' 'F' /* Access client configuration disk */
00071
00072 Say ""
00073 Say _mhdr "Setup complete"
00074 /*---------------------------------------------------------------------*/
00075 /* Common Exit point. */
00076 /*---------------------------------------------------------------------*/
00077 Profile_Exit:
00078 Exit rc

V11.3
EXempty
SYSTEM DTCPARMS D (for TCPMAINT)
00000 * * * Top of File * * *
00001 .**********************************************************************
00002 .* SYSTEM DTCPARMS created by DTCIPWIZ EXEC on 18 Oct 2018
00003 .* Configuration program run by MAINT at 11:59:17
00004 .**********************************************************************
00005 :nick.TCPIP :type.server
00006 :class.stack
00007 :attach.A000-A002
00008 :vnic.d000 system zl00lan2
00009
00010 :nick.FTPSERVE :type.server
00011 :class.ftp
00012 :anonymous.no
00013 * * * End of File * * *
TCPIP DATA F (for TCPMAINT)
===== * * * Top of File * * *

===== ; ----------------------------------------------------------------------
===== ; - TCPIP DATA created by DTCIPWIZ EXEC on 18 Oct 2018
===== ; - Configuration program run by MAINT at 11:59:36
===== ; ----------------------------------------------------------------------
===== ; %%File Origin Indicator - DO NOT REMOVE OR ALTER the next line%%
===== ; %%TCPIP%%TCPIP%%SDATA%%
===== ; ----------------------------------------------------------------------
===== TCPIPUSERID TCPIP
===== ; ----------------------------------------------------------------------
===== HOSTNAME ZVMB32
===== ; ----------------------------------------------------------------------
===== DOMAINORIGIN ILSVPN.IBM.COM
===== ; ----------------------------------------------------------------------
===== NSINTERADDR 10.31.160.2
===== NSINTERADDR 10.31.160.3
===== ; ----------------------------------------------------------------------
PROFILE TCPIP D (for TCPMAINT)
00000 * * * Top of File * * *

00001 ; ----------------------------------------------------------------------
00002 ; - PROFILE TCPIP created by DTCIPWIZ EXEC on 18 Oct 2018
00003 ; - Configuration program run by MAINT at 11:59:35
00004 ; ----------------------------------------------------------------------
00005 ; %%File Origin Indicator - DO NOT REMOVE OR ALTER the next line%%
00006 ; %%TCPIP%%PROFILE%%STCPIP%%
00007 ; ----------------------------------------------------------------------
00008 ACBPOOLSIZE 1000
00009 ADDRESSTRANSLATIONPOOLSIZE 1500

V11.3
EXempty
00010 CCBPOOLSIZE 150
00011 DATABUFFERPOOLSIZE 160 32K
00012 ENVELOPEPOOLSIZE 750
00013 FOREIGNIPPOOLSIZE 100
00014 IPROUTEPOOLSIZE 600
00015 LARGEENVELOPEPOOLSIZE 50 8192
00016 RCBPOOLSIZE 50
00017 SCBPOOLSIZE 256
00018 SKCBPOOLSIZE 256
00019 SMALLDATABUFFERPOOLSIZE 5
00020 TCBPOOLSIZE 256
00021 TINYDATABUFFERPOOLSIZE 10
00022 UCBPOOLSIZE 100
00023
00024 MONITORRECORDS
00025 SYSCONTACT
00026 Main Operator (555-1234)
00027 AlphaBeta Soup Corporation
00028 ENDSYSCONTACT
00029
00030 AUTOLOG
00031 ; CSMSERVE 0 ; CSM FTP Server
00032 FTPSERVE 0 ; FTP Server
00033 ; LDAPSRV 0 ; LDAP Server
00034 ; MPROUTE 0 ; Multiple Protocol Routing Server
00035 ; PORTMAP 0 ; Portmap server
00036 ; REXECD 0 ; REXEC Server
00037 ; SMTP 0 ; SMTP Server
00038 ; SNMPD 0 ; SNMP Agent Virtual Machine
00039 ; SNMPQE 0 ; SNMP Query Engine Virtual Machine
00040 ; SSLSERV 0 ; SSL Server
00041 ; UFTD 0 ; UFT Server
00042 ; VMNFS 0 ; NFS Server
00043 ENDAUTOLOG
00044
00045 OBEY
00046 OPERATOR TCPMAINT MAINT MPROUTE REXECD SNMPD SNMPQE LDAPSRV
00047 ENDOBEY
00048
00049
00050 ; ----------------------------------------------------------------------
00051 PORT
00052 20 TCP FTPSERVE NOAUTOLOG ; FTP Server
00053 21 TCP FTPSERVE ; FTP Server
00054 23 TCP INTCLIEN ; TELNET Server
00055 ; 25 TCP SMTP ; SMTP Server
00056 ; 111 TCP PORTMAP ; Portmap Server
00057 ; 111 UDP PORTMAP ; Portmap Server

V11.3
EXempty
00058 ; 161 UDP SNMPD ; SNMP Agent
00059 ; 162 UDP SNMPQE ; SNMPQE Agent
00060 ; 389 TCP LDAPSRV ; LDAP Server
00061 ; 389 UDP LDAPSRV ; LDAP Server
00062 ; 512 TCP REXECD ; REXECD Server (REXEC)
00063 ; 514 TCP REXECD ; REXECD Server (RSH)
00064 ; 520 UDP MPROUTE NOAUTOLOG ; Multiple Protocol Routing Server
00065 ; 608 TCP UFTD ; UFT Server
00066 ; 636 TCP LDAPSRV ; LDAP Server (Secure)
00067 ; 636 UDP LDAPSRV ; LDAP Server (Secure)
00068 ; 2049 UDP VMNFS ; NFS Server
00069 ; 2049 TCP VMNFS NOAUTOLOG ; NFS Server
00070 ; ----------------------------------------------------------------------
00071 DEVICE DEV@A000 OSD A000 NONROUTER
00072 LINK OSAA000 QDIOETHERNET DEV@A000 MTU 1500 IP
00073 DEVICE DEVD000 OSD D000 NONROUTER
00074 LINK OSAD000 QDIOETHERNET DEVD000 MTU 1500 IP
00075 ; (End DEVICE and LINK statements)
00076 ; ----------------------------------------------------------------------
00077 ; ----------------------------------------------------------------------
00078 HOME
00079 10.31.184.126 255.255.248.0 OSAA000
00080 192.168.1.126 255.255.255.0 OSAD000
00081 ; (End HOME Address information)
00082 ; ----------------------------------------------------------------------
00083 GATEWAY
00084 ; Network Subnet First Link MTU
00085 ; Address Mask Hop Name Size
00086 ; ------------- --------------- --------------- ---------------- -----
00087 DEFAULTNET 10.31.188.1 OSAA000 1500
00088 ; (End GATEWAY Static Routing information)
00089 ; ----------------------------------------------------------------------
00090 START DEV@A000
00091 START DEV@D000
00092 ; (End START statements)
00093 ; ----------------------------------------------------------------------
00094 * * * End of File * * *

V11.3
EXempty
Commands
netstat dev
VM TCP/IP Netstat Level 710 TCP/IP Server Name: TCPIP
Device DEV@A000 Type: OSD Status: Ready

Queue size: 0 CPU: 0 Address: A000 Port name: UNASSIGNED
IPv4 Router Type: NonRouter Arp Query Support: Yes
Link OSAA000 Type: QDIOETHERNET Port number: 0
Transport Type: IP
Speed: 1000000000
BytesIn: 23172 BytesOut: 0
Forwarding: Enabled MTU: 1500 IPv6: Disabled
IPv4 Path MTU Discovery: Disabled
Broadcast Capability: Yes
Multicast Capability: Yes
IPv4 VIPA ARP
Multicast Group Members
--------------- -------
224.0.0.1 1
Device DEV@D000 Type: OSD Status: Ready

Queue size: 0 CPU: 0 Address: D000 Port name: UNASSIGNED
IPv4 Router Type: NonRouter Arp Query Support: Yes
Link OSAD000 Type: QDIOETHERNET Port number: 0
Transport Type: IP
Speed: 1000000000
BytesIn: 0 BytesOut: 0
Forwarding: Enabled MTU: 1500 IPv6: Disabled
IPv4 Path MTU Discovery: Disabled
Broadcast Capability: Yes
Multicast Capability: Yes
IPv4 VIPA ARP
Multicast Group Members
--------------- -------
224.0.0.1 1
Ready; T=0.01/0.01 12:04:50

V11.3
EXempty
netstat home
netstat home
VM TCP/IP Netstat Level 710 TCP/IP Server Name: TCPIP
IPv4 Home address entries:
Address Subnet Mask Link VSWITCH

------- ----------- ------ -------
10.31.184.126 255.255.248.0 OSAA000 <none>
192.168.1.126 255.255.255.0 OSAD000 <none>
IPv6 Home address entries: None

Ready; T=0.01/0.01 12:05:16
query lan det

VSWITCH SYSTEM ZL00LAN2 Type: QDIO Connected: 1 Maxconn: INFINITE
PERSISTENT RESTRICTED NONROUTER Accounting: OFF
USERBASED LOCAL
VLAN Aware Default VLAN: 0001 Default Porttype: Access GVRP: Disabled
Native VLAN: 0001 VLAN Counters: OFF
MAC address: 02-00-00-00-00-01 MAC Protection: OFF
IPTimeout: 5 QueueStorage: 8
Isolation Status: OFF VEPA Status: OFF
Uplink Port:
State: Ready
PMTUD setting: EXTERNAL PMTUD value: 8992 Trace Pages: 8
RDEV: C000.P00 VDEV: 0600 Controller: DTCVSW1 ACTIVE
RDEV: C003.P00 VDEV: 0600 Controller: DTCVSW2 BACKUP
Adapter Connections: Connected: 1
Adapter Owner: TCPIP NIC: D000.P00 Name: UNASSIGNED Type: QDIO
Porttype: Access
RX Packets: 0 Discarded: 0 Errors: 0
TX Packets: 0 Discarded: 0 Errors: 0
RX Bytes: 0 TX Bytes: 0
Device: D000 Unit: 000 Role: DATA Port: 2177
VLAN: IPv4 0001 Assigned by system
VLAN: IPv6 0001 Assigned by system
Options: Broadcast Multicast IPv4 VLAN
Unicast IP Addresses:
192.168.1.126 MAC: 02-00-00-00-00-04
Multicast IP Addresses:
224.0.0.1 MAC: 01-00-5E-00-00-01

V11.3
Exercise 6. Servicing z/VM (VMSES/E)
EXempty
Estimated time
01:00
Overview
In this exercise, the students apply RSU and COR service envelopes, and query
status of service on the system
Objectives
• Run the DETERSE exec
• Run the SERVICE exec
• Run the VMFINFO exec
• Run the PUT2PROD exec
• Query service status
Requirements
• z/VM Installation Guide
• z/VM Service Guide

going to perform.

V11.3
EXempty
Part 1: Getting started
__ 1. Log on and IPL your second-level z/VM system.
Part 2: Load the service files from the RSU or COR

From the student CD, open the z/VM 7.1 Service Guide.
__ 2. Start with “Steps to receive, apply, and build preventative or corrective service” in Chapter 2,
page 8. Read notes 1-3.
__ 3. Because this is a lab environment, we skip the backup step. Go to Step 2 and log on to
MAINT710 as instructed.
__ 4. In this lab, we will load the RSU and PTF from an electronic service envelope file, so skip to
Step 3. We will use the 500 disk to store the service files, as suggested. For this lab, the
envelope files have already been downloaded from the IBM service website to the 192
DASD volume. So for substep 4-a, you must “retrieve” them from there. To do that,
a. Attach volume 192 to your virtual machine.
b. Access 192 and 500 with any available file modes.
__ 5. Copy the files for RSU and COR envelopes from the 192 disk to the 500 disk.
What command did you use? ___________________________________
__ 6. Detach the 192 disk and continue at substep 4-b.
__ 7. In substep 3-b, be sure to deterse UM35373, UM35366, and RSU1701 TERSLINK files on
the 500 disk. The RSU file will take a few moments, so be patient on that one.
Part 3: Install the RSU envelope

We will install the RSU service before the two COR (UM35373, UM35366), so perform substep 3-c
(SERVICE ALL RSU1701) for your newly created RSU Document SERVLINK file. You should see
several screens full of messages, beginning with:
VMFSRV2760I SERVICE processing started
__ 8. Perform step 4 -- VMFVIEW SERVICE. If you have problems, try to determine what needs
to be done. Were any memos to users referenced in these messages? ___________
____________,__________,__________,___________,_________________
__ 9. Perform VMFUPDAT SYSMEMO. Browse some of the components, like CMS, CP, and
OSA, and scroll down to section 4 to see why no memos were mentioned.
Part 4: Place the service into production

In the real world, you would now test the service. But because this is a lab environment, and in the
interest of time, we will skip this step and continue in the Service Guide to put these changes into
production (page 11). Read Notes 1-3, and then skip to Step 3.
You have now completed the installation of the RSU envelope for z/VM 7.1

V11.3
EXempty
Note: At the time this course was created, no RSU level newer than 1701 was available. So, you
will see the message “VMFP2P1217I There are no products to put into production” during the
PUT2PROD process. You see this message because this exercise applies an RSU that has
already been applied during the z/VM Installation exercise.
Part 5: Install a COR envelope

__ 10. Before we continue, we need to verify that this PTF is not already installed. To do this, we
use the SERVICE command and query the status of the UM35366 PTF.
Issue these commands:
service all status UM35366
What is the status of these PTFs? ___________________________________
You should have seen that these PTFs have not been received. You are about to receive
and apply it now.
Note: You have already issued the DETERSE command for PTF UM35366 & ,UM35373 so you
should see the SERVLINK files for the PTF on the C disk.
__ 11. Run the SERVICE exec against the UM35366 SERVLINK file.
__ 12. Run the SERVICE exec against the UM35373 SERVLINK file
__ 13. When this process is complete, use the VMFVIEW SERVICE command to determine what
happened. What component was serviced by this COR Envelope? _______
What do you need to do? _________________________
Part 6: Place the service into production

__ 14. Issue these commands:
What is the status of these PTFs? ___________________________________
__ 15. Complete the installation of this PTF by running the PUT2PROD exec as documented in the
Service Guide.
Issue these commands:
service all UM35373
What is the status of these PTFs now? ___________________________________
__ 16. If you have time, try the VMFINFO exec, which gives more or less the same information.
__ 17. This completes the lab. Shut down your second-level system, and log off from your student
virtual machine.
Congratulations, you have successfully completed the lab exercise.
End of exercise

V11.3
EXempty
Exercise solutions
*
ACCESS 500 C
listfile * terslink c (da
FILENAME FILETYPE FM FORMAT LRECL RECS BLOCKS DATE TIME

RSU1701 TERSLINK C1 F 1024 102888 25722 10/24/18 13:56:14
UM35366 TERSLINK C1 F 1024 219 55 10/24/18 13:56:14
UM35373 TERSLINK C1 F 1024 2166 542 10/24/18 13:56:14
deterse rsu1701 terslink c = servlink c

Ready; T=4.88/5.06 12:33:22
service all rsu1701

...several screens full of messages...
VMFSRV2760I SERVICE processing completed successfully
Ready; T=0.24/0.26 13:30:53
vmfview service (then press PF2)
put2prod
VMFUTL2767I Reading VMFINS DEFAULTS B for additional options

VMFP2P2760I PUT2PROD processing started
VMFUTL2204I Linking PMAINT 41D with link mode M
VMFP2P1217I There are no products to put into production.
VMFP2P2760I PUT2PROD processing completed successfully
Note: The RSU1701 was allready applied, during the z/VM installation
listfile UM* TERSLINK C
UM35366 TERSLINK C1
UM35373 TERSLINK C1
DETERSE UM35366 TERSLINK C = SERVLINK C

DETERSE UM35373 TERSLINK C = SERVLINK C
service all status um35366
:
VMFSRV1227I UM35367 is not received or applied
service all status um35373

V11.3
EXempty
:
VMFSRV1227I UM35373 is not received or applied
service all UM35366

service all UM35373
PUT2PROD
VMFP2P1233I The following products have been put into production. Recycle
the appropriate servers.
VMFP2P1233I CMSSFS VMHCDSFS
VMFP2P1239I CMS was serviced. Re-IPL CMS in all virtual machines running CMS
to use the new service.
VMFP2P2760I PUT2PROD processing completed successfully

VMFUTL2767I Reading VMFINS DEFAULTS B for additional options
VMFSRV2195I SERVICE ALL STATUS UM35366
VMFUTL2204I Linking PMAINT 41D with link mode RR
VMFSRV1226I CMSSFS (7VMCMS10%CMSSFS) PTF UM35366 status:
VMFSRV1226I RECEIVED 10/19/18 15:41:12
VMFSRV1226I APPLIED 10/19/18 15:41:12
VMFSRV1226I BUILT 10/19/18 15:41:16
VMFSRV1226I PUT2PROD 10/19/18 15:41:27 VM71
Alternative to SERVICE ALL STATUS:
vmfsetup servp2p cmssfs

vmfinfo servp2p cmssfs
VMFINFO Main Panel
Select one of the following. Then press enter.

PPF fileid ...... SERVP2P PPF D
Component name .. CMSSFS Setup ... NO
Product ID .....: 7VMCMS10 System .. VM

V11.3
EXempty
Options: S - select
Option Query
Product description
Product status
Product requisites
Product dependencies
S PTFs/APARs
Serviceable parts/usable forms
Miscellaneous
PRESS PF1 to list PTF status for CMSSFS:
PTF/APAR Queries
Enter a PTF or APAR number and type an option code. Then press Enter.
PPF fileid ...... SERVP2P PPF D
Component name .. CMSSFS Setup ... NO
Product ID .....: 7VMCMS10 System .. VM
PTF number ...... (PF1 to select from list of PTFs)
APAR number ..... (PF1 to select from list of APARs)
Options: S - select
Option Query
Status of PTF
Requisites/supersedes of PTF
Dependencies/superseding of PTF
User memo of PTF
Serviceable parts included by PTF
Abstract of APAR(s)
PTF Number - Help
The PTF (Program Temporary Fix) number is the identifier used for a
service package. A service package contains changes that correct prob-
lems which have been previously reported via APARs (Authorized Problem
Analysis Reports). A PTF can contain several APARS and can affect many
parts.
The list of PTF numbers displayed is the list of PTF numbers that can
be
selected. If an APAR number was specified prior to requesting the Help
function, then the PTFs listed all contain the specified APAR. If an

V11.3
EXempty
APAR number was not specified, then the PTFs listed are the PTFs which
have been received for the specified product.
Type an "S" next to one PTF number; then press enter.
Option PTFs
UM35366
Query Output - PTF Status
PPF fileid .....: SERVP2P PPF D

Component name .: CMSSFS Setup ..: NO
Product ID .....: 7VMCMS10 System .: VM
------------------------------------------------------------
PTF: UM35366
------------
Receive status: RECEIVED.10/19/18.15:41:12.MAINT710
Apply status: APPLIED.10/19/18.15:41:12.MAINT710

V11.3
Exercise 7. Linux installation on IBM Z
EXempty
Estimated time
03:30
Overview
This lab covers how to start the initial driver Linux system and use it to install a
Linux on IBM Z guest.
Objectives
After completing this exercise, you should be able to:
• Verify the prerequisites for installing Linux on IBM Z
• Boot an initial Linux system
• Perform the network setup for this initial Linux system
• Install a target Linux system
Introduction
Now you will prepare and perform the Linux on IBM Z installation.
Requirements
• This lab guide

For the installation exercise, make sure that the virtual machine has at least 512
MB of storage. This exercise will be done at first level to perform the installation.
Then, we will map the first-level disks to the LINUX1 virtual machine at second
level. We will use the DEVNO parameter for the mdisk definitions for LINUX1 to

V11.3
EXempty
allow this to work. If you are not familiar with this parameter of the MDISK
statement, review the parameter.

V11.3
EXempty
__ 1. Log on to your ZVMBnn virtual machine, called LINUX1.
Part 2: Prepare the environment

__ 2. Before you start the installation, make sure that you have at least 512 MB of storage for
your virtual machine.
__ a. Check your storage.
query virtual storage
00: Storage=512m
We will be performing the SUSE Linux Enterprise Server installation from the ZVMBnn
virtual machine. It would take too long if we did it from our second-level guest environment.
__ 3. Issue the QUERY VIRTUAL DEVICE command to check the availability of the DASD. Be
sure that you have 100-101. You will be using 100 and 101 initially, as shown in the previous
exercise drawing.
query v 100-101
query virtual 100-101
00: DASD 0100 3390 OX0160 R/W 10016 CYL ON DASD BD3D SUBCHANNEL = 0014
00: DASD 0101 3390 OX0161 R/W 3338 CYL ON DASD BD3C SUBCHANNEL = 0013
Ready; T=0.01/0.01 13:37:53
Note: These disks are minidisks at the first-level system. You will assign them to the
LINUX1 virtual machine later in the exercise.
__ 4. Issue the QUERY VIRTUAL OSA command to check the availability of the OSA
connections.
q v osa
OSA 1000 ON NIC 1000 UNIT 000 SUBCHANNEL = 000C
1000 DEVTYPE OSA VIRTUAL CHPID 0F OSD
1000 MAC 02-D0-31-00-00-04 CURRENT
1000 QDIO-ELIGIBLE QIOASSIST NOT AVAILABLE
OSA 1001 ON NIC 1000 UNIT 001 SUBCHANNEL = 000D
1001 MAC 02-D0-31-00-00-04 CURRENT
OSA 1002 ON NIC 1000 UNIT 002 SUBCHANNEL = 000E
1002 MAC 02-D0-31-00-00-04 CURRENT
__ 5. We use only the virtual OSA devices 1000-1002 for the Linux network connection.

V11.3
EXempty
Part 3: Transfer the Linux boot files to minidisk A
First, you need to boot a Linux starter system in memory. Later, this system is used to install your
Linux target system on disk. In order to boot Linux from your z/VM reader, three files must be
copied from the SUSE DVD1 to your z/VM 191 minidisk.
You will use the FTP command from your z/VM session to transfer the following files from the
FTP/NFS server to your VM A-disk:
▪ kernel (the Linux kernel)
▪ parmfile (install parameters)
▪ initrd (the initial file system)
Note
The initrd and kernel files must be transferred in binary mode. All three files must be
transferred with a fixed record length of 80 (FTP subcommands bin and locsite fix 80).
Instructor Note: The students will have a copy of the initrd, vmrdr.ikr, parmfile, and S11SP2 EXEC
on their 192 disk. They can copy these over and modify them if they have issues with the FTP
processes. You might find this helpful if you have to help them with their files in lab debugging.
Refer to the “Linux distribution server information” in Exercise 7 for the FTP/NFS server IP address,
user ID, password, and install directory.
In order to use the FTP command, you will need access to TCPMAINT’s 592 mdisk. If it is not
already linked to your virtual machine, you will use the vmlink command to gain access.
__ 6. From your LINUX1 virtual machine, QUERY DISK to see whether 592 is accessed. If not,
issue the following command:
vmlink tcpmaint 592
__ 7. Now use FTP to copy initrd, kernel, and parmfile to your 191 minidisk.
__ a. Begin with ftp 10.31.189.229.
__ b. At the user prompt, type in the lnxstudent.
__ c. At the password prompt, type in the lnx9stud.
__ d. Change the directory to where the linux image has been saved:
Linux Distros kernel initrd parmfile FTP directory
SuSE 15 linux initrd parmfile /sles15/dvd1/boot/s390x
Red Hat 7,5 kernel.img initrd.img generic.prm /rhel75/boot/images
Ubuntu 18.04 ubuntu.ikr initrd.ubuntu parmfile.ubuntu /ubuntu1804/dvd1/boot"
__ e. Change to the ftp directory listed on the preceding table: cd <ftp directory>
__ f. Change the image download to binary: bin
__ g. Change to fixed width: locsite fix 80
__ h. Get the initrd file shown in the table: get <initrd> linux.<initrd>
__ i. Get the kernel image shown in the table: get <kernel> linux.<kernel>

V11.3
EXempty
__ j. Change your mode to ASCII: ascii
__ k. Reset the fixed-width setting: locsite fix 80
__ l. Get the parameter file shown in the table: get <parmfile> linux.<parmfile>
__ m. Quit the FTP session: quit
Instructor example commands:
bin
>>>TYPE i
200 Switching to Binary mode.
Command:
locsite fix 80
Part 4: Prepare the files for the installation

__ 8. You must tell the installation program certain things, such as network devices and where the
installation files can be located. You can use the PARMFILE to predefine these parameters,
before starting the installation. Edit the PARMFILE that you have just downloaded from the
site.
__ a. Edit LINUX PARMFILE A
__ b. Type SET CASE MIXED at the XEDIT command line to allow for lower-case and
upper-case characters.
Note: It would be a very good idea to put this command in your PROFILE XEDIT so
that the command automatically executes every time that you enter XEDIT.
__ c. Remove the characters "manual=1"" from the end of the first line in the file.
__ d. In the prefix area of that line, type i6 to add six new lines to the file.
__ e. Using the “Network configuration information” in Exercise 7, add the following six lines.
(Use the “Linux TCPIP Stack Hostname table” to determine the <IPaddress> for your
team.)
SUSE PARMFILE:
ramdisk_size=131072 root=/dev/ram1 ro init=/linuxrc TERM=dumb
ReadChannel=0.0.1000 WriteChannel=0.0.1001 DataChannel=0.0.1002
Layer2=0 InstNetDev=osa OSAInterface=qdio ssl_certs=0
Install=ftp://lnxstudent:lnx9stud@10.31.189.229/sles15/dvd1
Portno=0 nameserver=10.31.160.2 gateway=10.31.188.1
UseVNC=1 VNCPassword=12345678 osahwaddr=
Broadcast=10.31.191.255 OsaMedium=eth
ifcfg=10.31.184.127/21,10.31.188.1,10.31.160.2,ilsvpn.ibm.com

V11.3
EXempty
REDHAT parmfile:
ro ramdisk_size=40000 cio_ignore=all,!condev
CMSDASD=191 CMSCONFFILE=redhat.conf
vnc
inst.repo=ftp://lnxstudent:lnx9stud@10.31.189.229/rhel75/dvd1/
RedHat requires the redhat.conf file to load the installation parameters. An example of this file is
shown below. You must change the values in red.
HOSTNAME="lnxzl3.ilsvpn.ibm.com"
DASD="0.0.0100"
NETTYPE="qeth"
IPADDR="10.31.185.144"
SUBCHANNELS="0.0.1000,0.0.1001,0.0.1002"
PORTNAME="FOOBAR"
NETWORK="10.31.184.0"
NETMASK="255.255.248.0"
BROADCAST="10.31.191.255"
SEARCHDNS="ilsvpn.ibm.com"
GATEWAY="10.31.188.1"
DNS="10.31.160.2"
MTU="1500"
LAYER2=0
VSWITCH="1"
RUNKS=0
UBUNTU parmfile:
ro locale=en_US auto=true priority=critical cio_ignore=01ff-0fff
url=ftp://lnxstudent:lnx9stud@10.31.189.229/preseed.seed
s390-netdevice/choose_networktype=qeth
s390-netdevice/qeth/layer2=false s390-netdevice/qeth/port=0
s390-netdevice/qeth/choose=0.0.1000-0.0.1001-0.0.1002
netcfg/get_ipaddress=10.31.184.127 netcfg/get_netmask=255.255.248.0
netcfg/get_gateway=10.31.188.1 netcfg/get_nameservers=10.31.160.2
netdevice/qeth/layer2=false netcfg/confirm_static=true
netcfg/use_autoconfig=0 netcfg/disable_dhcp=true
hostname=ZLIN12 domain=ilsvpm.ibm.com network-console/start=note
network-console/password=12345678 network-console/password-again=12345678
The file should look something like this when you are done:
ramdisk_size=65536 root=/dev/ram1 init=/linuxrc TERM=dumb
HostIP=10.31.184.1nn Gateway=10.31.188.1 Nameserver=10.31.160.2
InstNetDev=osa Netmask=255.255.248.0 Broadcast=10.31.191.255
OsaInterface=qdio OsaMedium=eth Layer2=0 ReadChannel=0.0.A010
WriteChannel=0.0.A011 DataChannel=0.0.A012 PortName=DONTCARE
INSTALL=ftp://lnxstudent:lnx9stud@10.31.189.229//sles11sp2/dvd1
UseVNC=1 VNCPassword=password

V11.3
EXempty
Instructor notes: Setting up the file this way should save some time for the students. It will also
prevent them from incorrectly typing the options, when they do the installation.
__ f. File your changes and exit.
__ 9. An exec is needed to punch the bootable starter Linux system to the z/VM card reader
(device address 00C) and to IPL (boot) it from that device. You might need to IPL the initial
starter Linux system on more than one occasion. Therefore, having this exec is very helpful.
__ a. Edit LINUX EXEC A
__ b. Go to the prefix area on the first line and type i9 to add nine lines to the file.
__ c. Type the following lines into the file:
/* Rexx Linux starter system exec */
'CP SPOOL CONS START *'
'CP SPOOL PUN *'
'CP CLOSE RDR'
'PUR RDR ALL'
'PUN LINUX KERNEL A (NOH'
'PUN LINUX PARMFILE A (NOH'
'PUN LINUX INITRD A (NOH'
'CH RDR ALL KEEP NOHOLD'
'IPL 00C CLEAR'
Instructor notes: These lines will do the following operations:
/**/ makes it so the REXX Interpreter will be used.
'CP SPOOL PUN *' sends the card punch output to the card reader.
'CP CLOSE RDR' closes the reader.
'PUR RDR ALL' purges the reader.
'PUN LINUX KERNEL A (NOH' sends the SLES kernel to the punch.
'PUN LINUX PARMFILE A (NOH' sends the parmfile to the punch.
'PUN LINUX INITRD A (NOH' sends the INITRD to the punch.
'CH RDR ALL KEEP NOHOLD' keeps a copy of the files in the reader.
'IPL 00C CLEAR' IPLs the card reader.
__ d. File your changes and exit the file.
Part 5: Start the installation on z/VM

__ 10. Run the LINUX EXEC from your LINUX1 virtual machine.
__ a. Type LINUX and press Enter to start the exec.
There will be several screens of messages. Clear them until you get the prompt.
Next, you should see the following message:
Loading Installation System (1/6) (20064 kB) - 0% 1% 2%
3% 4% 5% 6% ........

V11.3
EXempty
Clear the next few screens, and you should see:
Starting vnc server. . .
A log file will be written to: /var/log/YaST2/vncserver.log ...
***
*** You can connect to <host>, display :1 now with vncviewer
*** Or use a Java capable browser on http://<host>:5801/
***
(When YaST2 is finished, close your VNC viewer and return to this window.)
At this point, you must now open a VNC viewer and continue the installation there. There
should be an icon for the UltraVNC viewer on your desktop. If you didn’t already have one, you
should have installed it in Exercise 7. If you did not perform that task, return to Exercise 7, and
do it now. When you finish, return to the following step.
End of exercise

V11.3
Exercise 8. Linux networking
EXempty
Estimated time
00:45
Overview
This lab will show you how to add another network adapter to your Linux on IBM Z
server.
Objectives
After completing this exercise, you should be able to modify network configuration
files on a Linux server.
Introduction
When you started these labs, you used an OSA device that is connected to a
virtual switch. In Exercise 3. “z/VM directory maintenance” you added a virtual NIC
with devices at address 1000 through 1002. These devices are connected to a
SYSTEM owned VSWITCH named ZL00LAN2. During this lab, you will configure
the adapter on your Linux server that will use these devices.
There might be times when you would like to have a second network adapter for
your Linux server. For example, if you wanted your server to be on both a public
and private network, you can define a second nic in the user directory . You repeat
the lab steps to achieve that.
Requirements
• This lab guide
• An RHEL Linux on IBM Z distribution
• A predefined Virtual Switch NIC device at address 1000-1002

V11.3
EXempty
First Level z/VM
Virtual QDIO adapters
ZVMB21 ZVMB22 ZVMB30 ZVMB39

A000-A002 A010-A012
Virtual Switch ZL00LAN
z/VM LPAR OSA-Express
Same LAN segment
and subnet
Ethernet LAN
Network
Figure 8-1. First-level lab
Second Level z/VM 7.1.0

TCPIP RHEL
A000-A002 D000-D002 1000-1002
a
Virtual Switch ZL00LAN2
ZVMBnn C000-C002 C003-C005
Virtual Switch ZL00LAN Virtual Switch ZL00LAN1

z/VM LPAR
OSA-Express
10.31.184.0 192.168.1.0
Network Network
Figure 8-2. Second-level lab

V11.3
EXempty
__ 1. log on to your ZVMBnn virtual machine and IPL your z/VM 7.1.0 system.
__ 2. Log on to your RHEL virtual machine and IPL from disk 150.
__ 3. Run the script /usr/local/sbin/set_ip.sh. This will assign an IP address for your virtual NIC.
__ 4. Now you can SSH into your virtual machine by using the IP address that is assigned to NIC
1000. The credential to ssh into the machine is lnxzvmbnn and use the default student
password lnx9stud. The IP address that you assigned is not configured in the network
configuration file and in this lab we will do that.
Part 2: Validating environment

__ 5. Check on the virtual switch and your virtual NIC availability with the vmcp query vswitch
and vmcp virtual nic and vmcp q v osa commands.
lnxbnn:~ # sudo vmcp q vswitch
VSWITCH SYSTEM ZL00LAN2 Type: QDIO Connected: 2 Maxconn: INFINITE
PERSISTENT RESTRICTED NONROUTER Accounting: OFF
USERBASED
VLAN Aware Default VLAN: 0001 Default Porttype: Access GVRP: Disabled
Native VLAN: 0001 VLAN Counters: OFF
MAC address: 02-D0-21-00-00-01 MAC Protection: OFF
IPTimeout: 5 QueueStorage: 8
Isolation Status: OFF VEPA Status: OFF
Uplink Port:
State: Ready
PMTUD setting: EXTERNAL PMTUD value: 8992
RDEV: C000.P00 VDEV: 0600 Controller: DTCVSW2 ACTIVE
RDEV: C003.P00 VDEV: 0600 Controller: DTCVSW1 BACKUP
lnxbnn:~ # sudo vmcp q v nic

Adapter 1000.P00 Type: QDIO Name: FOOBAR Devices: 3
MAC: 02-D0-31-00-00-0B VSWITCH: SYSTEM ZL00LAN2
lnxbnn:~ # sudo vmcp q v osa
OSA 1000 ON NIC 1000 UNIT 000 SUBCHANNEL = 000A

1000 MAC 02-00-00-00-00-05 CURRENT
OSA 1001 ON NIC 1000 UNIT 001 SUBCHANNEL = 000B
1001 MAC 02-00-00-00-00-05 CURRENT
OSA 1002 ON NIC 1000 UNIT 002 SUBCHANNEL = 000C

V11.3
EXempty
1002 MAC 02-00-00-00-00-05 CURRENT
1002 QDIO ACTIVE QIOASSIST NOT AVAILABLE
1002
1002 INP + 01 IOCNT = 00000019 ADP = 044 PROG = 000 UNAVAIL = 084
1002 BYTES = 0000000000002400
1002 OUT + 01 IOCNT = 00000000 ADP = 000 PROG = 000 UNAVAIL = 128
1002 BYTES = 0000000000000000
1002 BYTES = 0000000000000000
1002 BYTES = 0000000000000000
1002 BYTES = 0000000000000000
__ 6. Copy your current network scripts to a backup directory.
__ b. Go to the /etc/sysconfig/network-scripts directory.
__ c. Make a copy of the ifcfg-enccw0.0.1000 file if there is any.
cp ifcfg-enccw0.0.1000 ifcfg-enccw0.0.1000.back
This will back up your current configuration and will make it easy to recover under the
3270 console if something goes wrong.
Part 3: Using s390-tool to configure the network

Now let’s simulate the addition of another nic to the Linux system, when a new nic is added in the
z/VM user directory. Before we start to add a nic in the Linux, we deactivate the exiting nic first.
__ 7. Issue the znetconf command to check the network device information. You will see the
configured network devices.
lnxbnn:~ # sudo znetconf -c
Device IDs Type Card Type CHPID Drv. Name State
--------------------------------------------------------------------------------
0.0.1000,0.0.1001,0.0.1002 1731/01 Virt.NIC QDIO 18 qeth enccw0.0.1000 online
__ 8. Log on your RHEL virtual machine on the z/VM 7.1 (ZMVMBnn).
__ 9. On the Linux console, issue znetconf -u command to bring down the network device.
znetconf -r 1000
Remove network device 0.0.1000 (0.0.1000,0.0.1001,0.0.1002)?
Warning: this may affect network connectivity!
Do you want to continue (y/n)?y
y
Successfully removed device 0.0.1000 (enccw0.0.1000)
__ 10. Check what network devices are available for this Linux server but not configured.
znetconf -u
Scanning for network devices...
Device IDs Type Card Type CHPID Drv.
------------------------------------------------------------

V11.3
EXempty
0.0.1000,0.0.1001,0.0.1002 1731/01 OSA (QDIO) 18 qeth
__ 11. Configure the network device
znetconf -a 0.0.1000
Scanning for network devices...
Ö82916.975354Ü qdio: 0.0.1002 OSA on SC f using AI:1 QEBSM:0 PRI:1 TDD:1 SIGA:RW
A
Ö82916.988766Ü qeth 0.0.1000: Device is a Virtual NIC QDIO card (level: V710)
Ö82916.988766Ü with link type Virt.NIC QDIO (portname: )
Ö82916.989123Ü qeth 0.0.1000: Hardware IP fragmentation not supported on eth0
Ö82916.989126Ü qeth 0.0.1000: Inbound source MAC-address not supported on eth0
Ö82916.989166Ü qeth 0.0.1000: VLAN enabled
Ö82916.989202Ü qeth 0.0.1000: Multicast enabled
Ö82916.989360Ü qeth 0.0.1000: IPV6 enabled
Ö82916.989430Ü qeth 0.0.1000: Broadcast enabled
Ö82916.989465Ü qeth 0.0.1000: Outbound TSO not supported on eth0
Ö82917.207076Ü IPv6: ADDRCONF(NETDEV_UP): enccw0.0.1000: link is not ready
Successfully configured device 0.0.1000 (enccw0.0.1000)
__ d. We will modify the ifcfg-enccw0.0.1000 file to add the IP address, the default netmask,
and default gateway.
__ e. Use your favorite text editor (eg: vi) to open the ifcfg-enccw0.0.1000 file for editing.
__ f. Add the information to add the IP address, default netmask, and gateway information for
the NIC. You also need to add information for NIC that is specific for IBM Z.
__ g. Save the configuration file and exit the editor
__ h. Reboot your virtual machine.
__ 12. After a few minutes SSH into your virtual machine again. Verify the configuration for your
new adapter.
lnxbnn:~ # ifconfig enccw0.0.1000
enccw0.0.1000: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.31.184.125 netmask 255.255.248.0 broadcast 10.31.191.255
ether 02:d0:31:00:00:0b txqueuelen 1000 (Ethernet)
RX packets 624 bytes 125883 (122.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 411 bytes 60923 (59.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
__ 13. Did you see your new adapter? _________________
__ 14. Use the PING command to ping your new OSA adapter on address 1000. Were you
successful? ______________
__ 15. Use the PING command to ping the 10.31.184.nn address of your z/VM 7.1.0 OSA device.
Were you successful? _____________________
__ 16. Leave your Linux server and z/VM 7.1.0 system up since you will have another short break
and lecture before the next exercise.
End of exercise

V11.3
Exercise 9. Linux system management
EXempty
Estimated time
00:45
Overview
This lab covers some of the system management tasks for Linux on IBM Z,
specifically regarding disk management.
Objectives
• Add DASD (Vdisk for swap) dynamically to a running Linux on IBM Z server
• Add swap space to a Linux on IBM Z server
• Perform the necessary steps to add DASD persistently
• Enable cpuplugd daemon and customize policy to assign CPU resources
automatically
Introduction
In this exercise, you will dynamically add a Vdisk for swapping to Linux on IBM Z
server and make that change persistently in the Linux server. You will also be able
to use cpuplugd to manage CPU resources automatically.
Requirements
• This lab guide
• A Linux on IBM Z server

V11.3
EXempty
In this exercise, the students will add a Vdisk for swapping to the Linux on IBM Z
server and make that change persistently in the Linux server. You will also be able
to use cpuplugd to manage CPU resources automatically.

V11.3
EXempty
Preface
Linux divides its physical RAM into chunks of memory called pages. Swapping is the process that
frees a page of memory by copying it to a preconfigured space on disk, called swap space. The
combined size of the physical memory and the swap space is the amount of virtual memory
available.
Swapping is necessary for two important reasons. First, when the system requires more memory
than is physically available, the kernel swaps out lesser used pages and gives that memory to
applications (processes) that need the memory immediately. Second, a significant number of the
pages that are used by an application during its startup phase might be used only for initialization,
and then never used again. The system can swap out those pages and free memory for other
applications, or even for disk cache.
Currently, there is a swap partition on the disk to handle the swap space for your Linux guest. As
your system acquires more and more load, you might need to dynamically add swap space. Also,
data on a swap drive does not have to be persistent across reboots. So, it is sometimes more
efficient to use a virtual disk rather than to allocate physical disks for swap. This lab will show you
the processes to add a Vdisk as swap device and make the changes persistently.
Running Linux on IBM Z provides you the capability to adjust CPU and memory resources
dynamically, without stopping the Linux server. In this lab, we will also show you the process to let
Linux adjust the CPU resources automatically, based on the defined policy.
Part 1: Add Vdisk dynamically for swap space

__ 1. If you closed your PuTTY session after the last exercise, log in as lnxzvmbxx, using a new
PuTTY session.
__ 2. View your current swap space with the cat /proc/swaps command.
lnxzvmbnn:~ # cat /proc/swaps
Filename Type Size Used Priority
/dev/dm-1 partition 720892 0 -1
__ 3. Verify that there is no device already at address 200 using the VMCP Q V 200 command.
lnxzvmbnn:~ # sudo vmcp q v 200
HCPQVD040E Device 0200 does not exist
Error: non-zero CP response for command 'Q 200': #40
__ 4. Define a virtual disk at address 200 with 200,000 blocks of space, by using the vmcp
define command.
lnxzvmbnn:~ # sudo vmcp define vfb-512 200 200000
DASD 0200 DEFINED
Instructor note: If the students do not have the authority to create a VDISK, they missed a step
in Exercise 4, CP system configuration. They were supposed to add a parameter to the feature
statement to allow for each virtual machine to create vdisks of up to 350000 blocks in size.

V11.3
EXempty
__ 5. Verify that there is now a disk at address 200.
lnxzvmbnn:~ # sudo vmcp q v 200
DASD 0200 9336 (VDSK) R/W 200000 BLK ON DASD VDSK SUBCHANNEL = 000D
__ 6. Remove the virtual disk 200 from the CIO device driver blacklist by using the cio_ignore
command.
lnxzvmbnn:~ # sudo cio_ignore -r 200
__ 7. Verify whether the dasd_fba_mod device driver has recognized the new DASD by looking at
the /sys/bus/ccw/drivers/dasd-fba directory to check whether a 0.0.0200 entry is
present.
lnxzvmbnn:~ # ls /sys/bus/ccw/drivers/dasd-fba/
0.0.0200 bind module uevent unbind
__ 8. List the /sys/bus/ccw/drivers/dasd-fba/0.0.0200 directory to find out which
attributes for this device are available.
lnxzvmbnn:~ # ls /sys/bus/ccw/drivers/dasd-fba/0.0.0200
alias eer_enabled modalias status
availability erplog online subsystem
cmb_enable expires power uevent
cutype failfast raw_track_access uid
devtype failfast_expires readonly use_diag
discipline failfast_retries reservation_policy vendor
driver last_known_reservation_state retries
__ 9. Use the cat command to view the online attribute.
lnxzvmbnn:~ # cat /sys/bus/ccw/drivers/dasd-fba/0.0.0200/online
0
If the response is zero (as shown), the device is offline.
__ 10. You also can use command lsdasd to check whether the device 200 is online or not.
lnxzvmbnn:~ # sudo lsdasd
Bus-ID Status Name Device Type BlkSz Size Blocks
=========================================================================
0.0.0150 active dasda 94:0 ECKD 4096 7042MB 1802880
__ 11. Use the chccwdev command to set the device online or offline. After you try those different
options, set the device back to online.
lnxzvmbnn:~ # sudo chccwdev -e 0.0.0200
Setting device 0.0.0200 online
Done
lnxzvmbnn:~ # sudo chccwdev -d 0.0.0200

Setting device 0.0.0200 offline
Done

V11.3
EXempty
__ 12. Verify whether the device is available and what the device name is using command lsdasd.
lnxzvmbnn:~ # sudo lsdasd
Bus-ID Status Name Device Type BlkSz Size Blocks
=======================================================================
0.0.0150 active dasda 94:0 ECKD 4096 7042MB 1802880
0.0.0200 active dasdb 94:4 FBA 512 97MB 200000
__ 13. Notice that within the /dev directory a device and partition file have been created for the
swap device on dasdb.
lnxzvmbnn:~ # ls /dev/dasd*
/dev/dasda /dev/dasda1 /dev/dasda2 /dev/dasdb /dev/dasdb1 /dev/dasd_eer
__ 14. Use mkswap /dev/dasdb1 to write the swap signature to this new device.
lnxzvmbnn:~ # sudo mkswap /dev/dasdb1
Setting up swapspace version 1, size = 99992 KiB
no label, UUID=a79ff27f-d01a-41bb-b3f5-ee6e3d003d24
__ 15. Activate the swap device with sudo swapon /dev/dasdb1.
__ 16. Reissue the cat /proc/swaps command to check the status of your swap devices.
lnxzvmbnn:~ # cat /proc/swaps
Filename Type Size Used Priority
/dev/dm-1 partition 720892 0 -1
/dev/dasdb1 partition 99992 0 -2
Part 2: Add the disk permanently

So far, we have dynamically added a swap disk, which is useful for satisfying a temporary
requirement. However, the swap disk is lost after the Linux is rebooted. In this part of the exercise,
you make the necessary modifications to ensure that the swap disk will be online automatically
after each reboot of your Linux server.
Note
For a Linux server that is running under z/VM, all the resources are defined in the Linux guest
machine’s user directory file. In the previous Part 1, you dynamically defined a Vdisk by using the
vmcp command. This Vdisk will be gone after you log off the guest from the z/VM. In this lab, we do
not go through the process of adding a disk to the z/VM user directory. So we assume that the vdisk
definition has been added to the user directory of the Linux guest machine.
To put a DASD device in Red Hat persistently, an easy way is to put the device address in
/etc/dasd.conf.
__ 17. Modify the /etc/dasd.conf file.
__ a. sudo vi /etc/dasd.conf
__ b. Move your cursor to the last line.

V11.3
EXempty
__ c. Type $ (This should put your cursor at the end of the line.)
__ d. Type i to put you in insert mode.
__ e. Press Enter key to input a new line
__ f. Add a new line with disk 0.0.0200
0.0.0150
0.0.0200
__ g. Type :wq
__ 18. Reboot your Linux server by using the sudo reboot command
__ 19. After the server comes back, log in using ssh. Issue sudo lsdasd command. You will see
that disk 200 is put on line automatically.
__ 20. Update /etc/fstab with an entry to activate the swap device automatically at the next
startup. (You might want to replicate the entry for the original swap volume and then update
the new entry).
lnxzvmbnn:~ # vi /etc/fstab
/dev/mapper/rhel_lnxzl3-root / xfs defaults 0 0
/dev/disk/by-path/ccw-0.0.0150-part1 /boot xfs defaults 0 0
/dev/mapper/rhel_lnxzl3-swap swap swap defaults 0 0
/dev/disk/by-path/ccw-0.0.0200-part1 swap swap defaults 0 0
Part 3: Using cpuplugd to manage CPU resources automatically

The cpuplugd daemon manages CPU and memory resources based on a set of rules. Depending
on the workload, CPUs can be enabled or disabled. You can increase or decrease the amount of
memory by using the Cooperative Memory Management (CMM1) feature. In this part, you use the
cpuplugd utility from s390-tools to let Linux manage CPU resources automatically. (You also can
set memory policies to let cpuplugd adjust memory resource automatically. But we won’t cover this
in this lab.)
__ 1. If you closed your PuTTY session after the last exercise, log on the Linux server as
lnxzvmbxx, using a new PuTTY session.
__ 2. Check the CPU information by using the lscpu command. It’s also a utility from s390-tools.
You also can check the CPU information by using the top command or from
/proc/cpuinfo. From the following command result, you see that there are 2 CPUs
configured and activated in this Linux server. They are defined in the z/VM user directory.
lnxzvmbnn:~ # sudo lscpu -e
CPU DRAWER BOOK SOCKET CORE L1d:L1i:L2d:L2i ONLINE CONFIGURED POLARIZATION ADDRESS
0 0 0 0 0 0:0:0:0 yes yes horizontal 0
__ 3. In this lab, in order to help you observe the automatic CPU adjustment by the Linux server,
you will need to edit the cpuplugd policy file /etc/sysconfig/cpuplugd.
__ a. Go to the line with HOTPLUG="((1 - CP_ActiveAVG) * onumcpus) < 0.08".
__ b. Change the line to HOTPLUG="idle < 80".

V11.3
EXempty
In this example, The Linux server will now activate an additional available CPU if the
system’s CPU idle time less than 80%. The HOTUNPLUG value means that the Linux
server will deactivate a CPU if the CPU usage is very low.
__ 4. Save the file.
__ 5. Check the cpuplugd service and start it. If the service is already running, you must restart it.
lnxzvmbnn:~ # sudo systemctl status cpuplugd.service
● cpuplugd.service - LSB: Start the cpu and memory hotplug daemon for Linux on
System z
Loaded: loaded (/etc/rc.d/init.d/cpuplugd; bad; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)

● cpuplugd.service - LSB: Start the cpu and memory hotplug daemon for Linux on
System z
Loaded: loaded (/etc/rc.d/init.d/cpuplugd; bad; vendor preset: disabled)
Active: active (running) since Thu 2018-11-08 03:23:51 EST; 2s ago
Docs: man:systemd-sysv-generator(8)
Process: 11621 ExecStart=/etc/rc.d/init.d/cpuplugd start (code=exited,
status=0/SUCCESS)
Main PID: 11636 (cpuplugd)
CGroup: /system.slice/cpuplugd.service
└─11636 /usr/sbin/cpuplugd -c /etc/sysconfig/cpuplugd
Nov 08 03:23:50 lnxzl3.ilsvpn.ibm.com systemd[1]: Starting LSB: Start the cpu and
memory hotplug daemon for Linux on System z...
Nov 08 03:23:51 lnxzl3.ilsvpn.ibm.com cpuplugd[11621]: Starting cpuplugd: [ OK ]
Nov 08 03:23:51 lnxzl3.ilsvpn.ibm.com cpuplugd[11636]: Waiting 3 intervals to
accumulate history.
Nov 08 03:23:51 lnxzl3.ilsvpn.ibm.com systemd[1]: Started LSB: Start the cpu and
memory hotplug daemon for Linux on System z.
__ 6. Now, take a look at the CPU status by using the lscpu command. Because the CPUs in the
Linux server do not do any workload, you will see that CPU 1 is deactivated by cpuplugd
automatically.
lnxzvmbnn:~ # sudo lscpu -e
1 - - - - ::: no yes horizontal 1
__ 7. Now let’s run something on the Linux server to boost the CPU utilization and observe how
the number of CPUs changes on the system. In the current ssh session, issue the following
command to keep issuing the lscpu command. Whenever the CPU status changes, it will
be highlighted. In the following command, the default refresh time is 2 seconds.
lnxzvmbnn:~ # sudo watch -d lscpu -e
Every 2.0s: lscpu -e
Thu Nov 8 03:43:48 2018

V11.3
EXempty
1 - - - - ::: no yes horizontal 1
__ 8. Open a new PuTTY window to log in the Linux server with a separate ssh session. In the
new ssh session window, issue the yum update command to increase the CPU utilization
slightly. (You can ignore any outputs from the yum command.). You can also use any other
methods to boost up the CPU utilization. After you issue that command, go to the previous
ssh session window, and you will see automatic activation of the CPU 1 within a couple
seconds. After the yum command is complete, you will see that the CPU 1 is deactivated
again.
Every 2.0s: lscpu -e
Thu Nov 8 03:52:40 2018
__ 9. Stop the watch command with Ctrl+C keys.
End of exercise

V11.3
Exercise 10. z/VM Performance Toolkit configuration
EXempty
Exercise 10. z/VM Performance Toolkit

configuration
Estimated time
01:30
Overview
This lab covers how to configure the z/VM Performance Toolkit program product.
Objectives
• Enable and configure the z/VM Performance Toolkit product
• Activate and use the 3270 and web interfaces for z/VM Performance Toolkit
Introduction
In this exercise, you will plan, enable, configure, and implement z/VM
Performance Toolkit.
Requirements
• This lab guide
• z/VM Performance Toolkit Program Directory

The first part of this exercise covers how to enable and configure Performance
Toolkit. After that, the students will use the 3270 and web interfaces to view the
panels available for this product.

V11.3
EXempty
Part 1: Log on to the student guest system
__ 1. Set up and IPL your second-level z/VM system.
Part 2: Full screen console mode for the system operator

For this exercise, OPERATOR must capture and save system information. To do this, it will need to IPL
CMS.
__ 2. Verify that you are currently logged on to the OPERATOR virtual machine.
__ 3. Issue the Query Disk command. Were you successful? __________
__ 4. If not, that indicates that ZCMS has not been IPLed. If so, issue IPL ZCMS in the OPERATOR
virtual machine so that it can use CMS commands. (ZCMS is a requirement for executing the
PERFKIT module, because it enables CMS programs to use z/Architecture instructions.)
__ 5. Log off from OPERATOR and log on to MAINT.
__ 6. Edit the USER DIRECT file, and verify that the OPERATOR virtual machine’s entry includes the
OPTION LNKNOPAS statement. If it does not, add the statement.
__ 7. Edit the USER DIRECT file, and verify that the OPERATOR virtual machine’s entry includes the
IPL ZCMS PARM AUTOCR statement. If it does not, add the statement.
__ 8. If you made any changes, save your work, and put the directory on line.
__ 9. Log off from MAINT and log on to OPERATOR.
__ 10. Modify the PROFILE EXEC.
__ a. Add a link to PERFSVMs 201 mdisk.
__ b. Add an access of that mdisk.
__ c. Add an entry to start the PERFKIT MODULE.
__ 11. Execute the PROFILE EXEC command to implement those updates.
__ 12. Were you successful? ________________
__ 13. Issue the Query PRODUCT command. What is the status of the Performance Toolkit for VM
product? ________________________
__ 14. Open the previously created PCOMM session to the IP address of your z/VM TCPIP stack that is
on the 10.31.184.0 subnet.
__ 15. Log on to MAINT710.
__ 16. Issue the following commands:
SERVICE PERFTK ENABLE
__ 17. Verify that the product was enabled successfully.
__ 18. From OPERATOR, run PROFILE EXEC again. Did the PERFKIT module execute successfully
this time? _____________

V11.3
EXempty
__ 19. Issue the Query Names command at the Performance Toolkit command line to see what virtual
machines are currently logged on to the system.
__ 20. Issue several trivial commands until the screen has filled up and the older messages roll off the
display.
__ 21. Press the appropriate PF key to redisplay the old messages.
__ 22. What key did you select? _______________________
__ 23. Use the PF7 and PF8 key to scan through the PERFKIT log. This log is on the 191 disk of the
OPERATOR.
__ 24. Use the FILELIST command to display all the files on Operator's 191 disk, and then edit the
PERFKIT console log.
__ 25. What is the name of this file? ____________ ________________
Note: This log is appended for a 24-hour period.
__ 26. Close the XEDIT session and filelist display.
__ 27. Disconnect from the OPERATOR virtual machine.
Part 3: Enable and configure Performance Toolkit for z/VM 7.1

__ 28. Open the Program Directory for z/VM Performance Toolkit (on the CD that was delivered with the
student materials). You will follow the steps that are described in Chapter 6.0 “Installation
Instructions”. Review 6.1 “Performance Toolkit for VM Enablement and Customization Process
Overview.” Before you begin the process, return to your MAINT710 PCOMM session and issue
the CP Query PRODUCT command.
__ 29. What is the status of the Performance Toolkit for VM? _______________
Note: You would normally need to enable this product as documented in 6.2 “Enable
Performance Toolkit for VM.” (To do this, you are referred to the MEMO TO USERS for the
product.) However, because we already enabled Performance Toolkit for VM to allow
OPERATOR to execute the PERFKIT MODULE, skip this task.
__ 30. Continue with 6.3. “Tailoring Performance Toolkit for VM Customization Files”.
Note: Since you are not performing a migration, you do not need to read section 5.2.
The only file that you will need to tailor for this exercise will be FCONX $PROFILE file. Since you
are already logged on to MAINT710, skip to instruction 2 (page 14). Create a local modification
for this file and verify that the following parameters are uncommented and/or modified
appropriately:
FC MONCOLL CPMON DCSS ON MONDCSS
FC MONCOLL VMCF ON
FC MONCOLL WEBSERV TIMEOUT 30
FC MONCOLL WEBSERV ON TCPIP TCPIP 81
FC MONCOLL LINUXUSR ON TCPIP TCPIP
FC USERBOTL BASIC F1=Help F2=Log F3=Quit F4 Monitor F11=Retr F12=Return
__ 31. Save your work when you are finished.

V11.3
EXempty
__ 32. Before you go on to instruction 3, issue the following command:
VMFSETUP SERVP2P PERFTKSFS (LINK
__ 33. Use the FILELIST command to show all the files on the E disk. These are the files that were
created by the LOCALMOD command. Examine the contents of these files. These files are not
currently usable by PERFSVM. You will correct this when we build the PERFTK product.
__ 34. Now, continue with instruction 3 to build Performance Toolkit.
__ 35. Complete 6.4 “Place Performance Toolkit for VM Into Production”.
__ 36. Complete 6.5 “Post-Installation Considerations”. Ignore the error message that you see
concerning FCONX LINUXUSR when you start PERFKIT. You will fix this shortly. Also, because
this is the last exercise, don’t bother to put PERFSVM into AUTOLOG1’s PROFILE EXEC.
__ 37. From your MAINT710 session, issue the Query CPUID command. Make note of the first 6 digits
after “FF”. What is the CPUID? _____________________
__ 38. Update the SYSTEM NETID on MAINT’s 190 and MAINT710’s 490 with the appropriate values
for the CPUID, NODEID, and NETID. Refer to the lecture if you are not sure what these values
should be.
__ 39. Again, save the CMS saved segments with the PUT2PROD SAVECMS command.
__ 40. Issue the Query PRODUCT command. What is the status of Performance Toolkit for VM?
_____________________
__ 41. Log off from MAINT710, and close that PCOMM session.
__ 42. On your remaining PCOMM session, log on to the PERFSVM virtual machine. Press Enter. You
should see a screen similar to what we saw on the OPERATOR virtual machine after we started
the PERFKIT Module. Press the PF12 key to exit from this screen.
__ 43. Edit the PROFILE EXEC file and uncomment all the CP MONITOR statements at the bottom of
the file, except for the SSI statements. Add these MONITOR EVENT statements to the PROFILE
EXEC:
'CP MONITOR EVENT ENABLE PROCESSOR'
'CP MONITOR EVENT ENABLE SCHEDULER ALL'
'CP MONITOR EVENT ENABLE USER ALL'
'CP MONITOR EVENT ENABLE APPLDATA ALL'
__ 44. Create the following files, with the appropriate information.
__ UCOMDIR NAMES - Insert the following information:
:nick.FCXRES00 :luname.*IDENT
:tpn.FCXC1R01
:security.SAME
:nick.FCXSYSTM :luname.*IDENT
:tpn.FCXC1S01
:security.SAME
__ FCONRMT SYSTEMS - Insert the appropriate entry for your system. (Notice that the third
parameter is a placeholder and can be anything that you like, but it is critical that the other four
parameters are specified correctly.)

V11.3
EXempty
__ FCONRMT AUTHORIZ - Authorize PERFSVM (for S&FSERV and DATA), MAINT, and
OPERATOR (for DATA, CMD, and EXCPMSG) and DATA only for all other users.
__ FCONX LINUXUSR - Insert these 3 pre-installed Linux servers:
SLES15 10.31.185.142:8803
UBUN18 10.31.185.143:8803
RHEL75 10.31.185.144:8803
__ 45. Add also your preinstalled Linux server RHEL using IP Address 10.31.184.xxx. If it is not active,
you can start it using this command: XAUTOLOG RHEL
__ 46. Start the PERFKIT MODULE by running the PROFILE EXEC in the PERFSVM virtual machine.
(Ignore the message about the TCP/IP error 13 on socket. You will fix this in just a moment.)
__ 47. Were you successful? ______________
__ 48. Did you see the PERFKIT main menu? _____________________
Part 4: Performance Toolkit System Management Facility web interface

__ 49. Log off PERFSVM and log on to TCPMAINT.
__ 50. Reserve PORT 81 for PERFSVM in the PROFILE TCPIP file, and verify that the
MONITORRECORDS statement is specified.
__ 51. Recycle TCPIP with netstat cp ipl cms parm autocr. This will reestablish the TCP/IP path
between these two virtual machines.
__ 52. Ping 10.31.188.1 to verify that TCPIP is working correctly.
__ 53. Start Performance Toolkit by entering, XAUTOLOG PERFSVM
__ 54. LOGOFF from TCPMAINT.
Part 5: Web interface testing
Note
At the time that this guide was published, the next steps work with IE 8, Firefox, and Chrome
browsers only.
__ 55. Enter the URL for your Performance Toolkit application (10.31.184.nnn:81) into your desktop
browser.
__ 56. Did you connect to your Performance Toolkit application? __________________
If not, contact your instructor for assistance, unless you can debug this problem on your own.
__ 57. Enter a Performance Toolkit-authorized virtual machine name and password, and select
SUBMIT.
__ 58. Select your system name from the System Accessible in the APPC/VM screen.
__ 59. Is the Initial Data Performance Selection Menu screen displayed? _____________________

V11.3
EXempty
__ 60. Examine several of the menu selections from this screen. Notice the MENU button at the top
when you are in a selection window. This button will return the viewer to the main menu for
Performance Toolkit for VM.
__ 61. Select the LINUX Systems menu option (under User Data), and drill down until you see the
three pre-installed Linux guests that you added in FCONX LINUXUSR. You should be able to
view performance data for these pre-installed Linux servers.
Note
RMF PM in this lab is pre-installed in three Linux servers and in the RHEL preinstalled Linux that
you have used for the Linux network and System Management exercises.
__ 62. This concludes this lab. Shut down your Linux guest system, and then your z/VM system, and log
off your student virtual machine.
Congratulations! You have completed the course.
Please complete the course evaluation and have a safe trip home.
End of exercise

V11.3
EXempty
Exercise solutions
These solutions are for team ZVMBxx.
/********************************/
/* Operator/OP1 Profile Exec */
/********************************/
Address Command
'SYNONYM SYN'
'CP TERMINAL MODE VM'
'CP SPOOL CONSOLE * START' q
'CP SET RUN ON'
'CP SET PF11 RETRIEVE FORWARD'
'CP SET PF23 RETRIEVE FORWARD'
'CP LINK PERFSVM 201 201 RR'
Address cms 'acc 201 g'
Address cms 'perfkit'
PROFILE EXEC A1 V 130 Trunc=130 Size=56 Line=0 Col=1 Alt=

====>
0 * * * Top of File * * *
1 /**********************************************************/
2 /* THIS EXEC IS RESTRICTED MATERIAL OF IBM */
3 -------------------- 16 line(s) not displayed -----------
19 'PIPE CP LINK MAINT 193 193 RR | HOLE'
20 'ACCESS 193 R/R'
21
22 /* Set up disk access using production level disks.
23 'ACCESS 19D F ' /* Help files
24 'ACCESS 201 B ' /* Production Disk
25 'ACCESS 1CC D ' /* Customized controls disk
26
27 -------------------- 11 line(s) not displayed -----------
/*** Once you have PERFKIT enabled and running uncomment */
/*** the following comments */
'CP MONITOR SAMPLE ENABLE PROCESSOR'
'CP MONITOR SAMPLE ENABLE STORAGE'
'CP MONITOR SAMPLE ENABLE USER ALL'
'CP MONITOR SAMPLE ENABLE I/O ALL'
'CP MONITOR SAMPLE ENABLE NETWORK' /*ØF1153MP*/
'CP MONITOR SAMPLE ENABLE APPLDATA ALL'
'CP MONITOR SAMPLE ENABLE ISFC' /*ØF1153MP*/
/* 'CP MONITOR SAMPLE ENABLE SSI' */ /*ØF1153MP*/
'CP MONITOR EVENT ENABLE PROCESSOR'
'CP MONITOR EVENT ENABLE SCHEDULER ALL'

V11.3
EXempty
'CP MONITOR EVENT ENABLE STORAGE'
'CP MONITOR EVENT ENABLE USER ALL'
'CP MONITOR EVENT ENABLE I/O ALL'
'CP MONITOR EVENT ENABLE NETWORK' /*ØF1153MP*/
'CP MONITOR EVENT ENABLE APPLDATA ALL'
'CP MONITOR EVENT ENABLE ISFC' /*ØF1153MP*/
/* 'CP MONITOR EVENT ENABLE SSI' */ /*ØF1153MP*/
FCONX $PROFILE D2 F 80 Trunc=80 Size=460 Line=188 Col=1 Alt=0

====>
* Following command for MONITOR data extraction from MONDCSS segment
FC MONCOLL CPMON DCSS ON MONDCSS
* Following command to start populating formatted output collector
*C MONCOLL SEGOUT ON PERFOUT
* data on disk during the specified time period
FC MONCOLL PERFLOG ON 06:00 19:59 MO-FR
* Following command activates VMCF data retrieval interface
FC MONCOLL VMCF ON
* Define the maximum allowed number of Internet connections
FC MONCOLL WEBSERV MAXCONN 100
* Define the timeout of inactive Internet connections in minutes
FC MONCOLL WEBSERV TIMEOUT 30
* Following command activates Internet interface
FC MONCOLL WEBSERV ON TCPIP TCPIP 81
* Following command activates Internet interface with SSL
*C MONCOLL WEBSERV ON SSL TCPIP TCPIP 81
* Following command activates TCP/IP interface for data retrieval
* from LINUX RMF DDS interface
FC MONCOLL LINUXUSR ON TCPIP TCPIP
FC USERBOTL BASIC F1=Help F2=Log F3=Quit F4 Monitor F11=Retrieve F12=Return
*---------------------------------------------------------------------*
* Activate the Emergency Safeguard Feature (ESF) of PERFKIT *
*---------------------------------------------------------------------*
UCOMDIR NAMES A1 V 255 Trunc=255

====>
0 * * * Top of File * * *
1 :nick.FCXRES00 :luname.*IDENT
2 :tpn.FCXC1R01
3 :security.SAME
4 :nick.FCXSYSTM :luname.*IDENT
5 :tpn.FCXC1S01
6 :security.SAME
7 * * * End of File * * *
FCONX LINUXUSR A1 F 80 Trunc=80
====>

V11.3
EXempty
* * * Top of File * * *
00001 SLES15 10.31.185.142:8803
00002 UBUN18 10.31.185.143:8803
00003 RHEL75 10.31.185.144:8803
00003 RHEL 10.31.184.xxx:8803
* * * End of File * * *
FCONRMT AUTHORIZ A1 F 80 Trunc=80 Size=4

====>
* * * Top of File * * *
ZVMBxx PERFSVM S&FSERV
ZVMBxx MAINT DATA CMD EXCPMSG
ZVMBxx OPERATOR DATA CMD EXCPMSG
ZVMBxx * DATA
* * * End of File * * *
FCONRMT SYSTEMS A1 F 80 Trunc=80 Size=1

====>
00000 * * * Top of File * * *
00001 ZVMBxx PERFSVM ZVM7.1 N FCXRES00
00002 * * * End of File * * *
PROFILE TCPIP D1 V 80 Trunc=80 Size=122

====>
77 PORT
78 20 TCP FTPSERVE NOAUTOLOG ; FTP Server
79 21 TCP FTPSERVE ; FTP Server
80 23 TCP INTCLIEN ; TELNET Server
81 ; 25 TCP SMTP ; SMTP Server
82 81 TCP PERFSVM ; PERFSVM
83 ; 111 TCP PORTMAP ; Portmap Server
84 ; 111 UDP PORTMAP ; Portmap Server
85 ; 143 TCP IMAP ; IMAP Server
86 ; 161 UDP SNMPD ; SNMP Agent
87 ; 162 UDP SNMPQE ; SNMPQE Agent
88 ; 389 TCP LDAPSRV ; LDAP Server
89 ; 389 UDP LDAPSRV ; LDAP Server
90 ; 512 TCP REXECD ; REXECD Server
91 ; 514 TCP REXECD ; REXECD Server
92 ; 520 UDP MPROUTE NOAUTOLOG ; Multiple Protocol
93 ; 608 TCP UFTD ; UFT Server
--------------------------------------------------------
113 MONITORRECORDS ; This will populate option 3K in PERFSVM
x

V11.3
Exercise A. z/VM 7.1 installation worksheets
AP
Exercise A. z/VM 7.1 installation

worksheets
The following pages show the following essential tables from the z/VM 7.1 installation worksheets:
Tables 1, 2, 3, 5, and 23.
© Copyright IBM Corp. 2007, 2018 A-1

V11.3
AP

V11.3
AP

V11.3
backpg
Global Learning and Skills Engineering
© Copyright International Business Machines Corporation 2007, 2018.

ZL002 Xinst

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

ZL002 Xinst

Transféré par

Droits d'auteur :

Formats disponibles

V11.

Global Learning and Skills Engineering

Instructor exercises overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Exercise 1. z/VM log on overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Exercise 2. z/VM installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Exercise 3. 7.1 CP system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Exercise 4. z/VM User Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Exercise 5. z/VM networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

© Copyright IBM Corp. 2007, 2018 ii

TOC Exercise 6. Servicing z/VM (VMSES/E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Exercise 7. Linux installation on IBM Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Exercise 8. Linux networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Exercise 9. Linux system management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Exercise 10. z/VM Performance Toolkit configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Exercise A. z/VM 7.1 installation worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

© Copyright IBM Corp. 2007, 2018 iii

© Copyright IBM Corp. 2007, 2018 iv

© Copyright IBM Corp. 2007, 2018 v

© Copyright IBM Corp. 2007, 2018 vi

Exercise 1. z/VM log on overview

© Copyright IBM Corp. 2007, 2018 1-1

Samon: Log on screen

© Copyright IBM Corporation 2007, 2018

© Copyright IBM Corp. 2007, 2018 1-2

MOPEDVM2: System logo

==== ======== ==== ====

Fill in your USERID and PASSWORD and press ENTER

Samon: Log on screen © Copyright IBM Corporation 2007, 2018

© Copyright IBM Corp. 2007, 2018 1-3

Log on with the BY option

LOGON userid (Example: LOGON VMUSER1)

logon ZVMB21 by SZVMB21

Samon: Log on screen © Copyright IBM Corporation 2007, 2018

© Copyright IBM Corp. 2007, 2018 1-4

Enter your password,

Samon: Log on screen © Copyright IBM Corporation 2007, 2018

© Copyright IBM Corp. 2007, 2018 1-5

TCP/IP lab introduction: Network connections

A000- A010- A000- A010- A010- A000-

ZVMB21 ZVMB22 ZVMB2n

Samon: Log on screen © Copyright IBM Corporation 2007, 2018

© Copyright IBM Corp. 2007, 2018 1-6

Exercise 2. z/VM installation

Instructor exercise overview

© Copyright IBM Corp. 2007, 2018 2-1

Part 1: Installation requirements

© Copyright IBM Corp. 2007, 2018 2-2

Part 2: Preparing to install your z/VM 7.1 non-SSI system

© Copyright IBM Corp. 2007, 2018 2-3

Part 3: Installing your z/VM 7.1 non-SSI system

© Copyright IBM Corp. 2007, 2018 2-4

Part 4: Editing files on the z/VM system

© Copyright IBM Corp. 2007, 2018 2-5

Part 5: Updating the PROFILE XEDIT

© Copyright IBM Corp. 2007, 2018 2-6

Part 6: Moving PROFILE XEDIT to the system disk

© Copyright IBM Corp. 2007, 2018 2-7

© Copyright IBM Corp. 2007, 2018 2-8

© Copyright IBM Corp. 2007, 2018 2-9

© Copyright IBM Corp. 2007, 2018 2-10

© Copyright IBM Corp. 2007, 2018 2-11

10:28:41 * DUPLICATION RESTRICTED BY GSA ADP SCHEDULE *

z/VM DASD DUMP/RESTORE PROGRAM