Front cover

IBM System z
Personal Development Tool
Volume 2 Installation and Basic Use

System z Development Tool

Full z/OS usage

Linux base

Bill Ogden

ibm.com/redbooks
.
International Technical Support Organization

IBM System z Personal Development Tool: Volume 2

Installation and Basic Use

July 2011

SG24-7722-03
 Note: Before using this information and the product it supports, read the information in “Notices” on page v.

Fourth Edition (July 2011)

This edition applies to the IBM 1090 system (known as zPDT) that is available at the time of publication.

© Copyright International Business Machines Corporation 2009, 2011. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM Corp.
Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
The author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Now you can become a published author, too! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Stay connected to IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Chapter 1. Linux and 1090 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1 Disk planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Linux installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.1 x3270 keyboard maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2.2 Other Linux notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3 Install the 1090 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3.1 Alter Linux files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.4 1090 serial numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5 1090 hardware key activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.5.1 IBM Resource Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.6 Installing a new 1090 release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 2. AD CD z/OS installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.1 General principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.2 System z operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.2.1 Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3 Packages for the 1090 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4 Installing an AD-CD system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4.1 Specific installation instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4.2 IODF device numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.4.3 1090 control files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4.4 IPL and operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.4.5 Shutting down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.6 Startup messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.4.7 Local volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.5 z/OS parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.6 Multiple operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 3. LANs and TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.1 Overview of LAN usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.1.1 Three 3270 interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.2 Basic QDIO setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.3 Five scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.3.1 Scenario 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.3.2 Scenario 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3.3 Scenario 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.3.4 Scenario 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.3.5 Scenario 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.3.6 z/OS resolver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.3.7 Debugging LAN setups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

© Copyright IBM Corp. 2009, 2011. All rights reserved. iii

 3.3.8 Performance problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.3.9 Detailed scenario comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.4 Wireless connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.5 Telnet to z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.6 Choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.7 Useful networking commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 4. Using basic zPDT commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4.1 Setup commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.2 Basic operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.3 CP commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.4 Devmaps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 5. Frequently asked questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Appendix A. z/OS 1.12 AD-CD example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

A.1 Disk planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
A.2 Connectivity planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
A.3 Listings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
How to get Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

iv IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult
your local IBM representative for information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or imply that only that IBM product,
program, or service may be used. Any functionally equivalent product, program, or service that does not
infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to
evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The
furnishing of this document does not give you any license to these patents. You can send license inquiries, in
writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time
without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring
any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm the
accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them
as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the sample
programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,
cannot guarantee or imply reliability, serviceability, or function of these programs.

© Copyright IBM Corp. 2009, 2011. All rights reserved. v

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines
Corporation in the United States, other countries, or both. These and other IBM trademarked terms are
marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US
registered or common law trademarks owned by IBM at the time this information was published. Such
trademarks may also be registered or common law trademarks in other countries. A current list of IBM
trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml

The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:
CICS® Redbooks (logo) ® z/Architecture®
DB2® Resource Link™ z/OS®
IBM® S/390® z/VM®
MVS™ System z® z/VSE™
PartnerWorld® VTAM® zSeries®
Redbooks® WebSphere®

The following terms are trademarks of other companies:

Intel, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countries.

Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States,
other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

SUSE, the Novell logo, and the N logo are registered trademarks of Novell, Inc. in the United States and other
countries.

Red Hat, and the Shadowman logo are trademarks or registered trademarks of Red Hat, Inc. in the U.S. and
other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.

vi IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
Preface

This IBM® Redbooks® publication introduces the IBM System z® Personal Development
Tool (zPDT), which runs on an underlying Linux system based on an Intel processor. zPDT
provides a System z system on a PC capable of running current System z operating systems,
including emulation of selected System z I/O devices and control units. It is intended as a
development, demonstration, and learning platform and is not designed as a production
system.

This book, providing specific installation instructions, is the second of three volumes. The first
volume describes the general concepts of zPDT and a syntax reference for zPDT commands
and device managers. The third volume discusses more advanced topics that may not
interest all zPDT users. The OBM order numbers for the three volumes are SG24-7721,
SG24-7722, and SG24-7723.

The systems discussed in these volumes are complex, with elements of Linux (for the
underlying PC machine), z/Architecture® (for the core zPDT elements), System z I/O
functions (for emulated I/O devices), and z/OS® (providing the System z application
interface), and possibly with other System z operating systems. We assume the reader is
familiar with the general concepts and terminology of System z hardware and software
elements and with basic PC Linux characteristics.

The author
This series of IBM Redbook publications was produced by the zPDT development team, with
assistance from many other people.

Bill Ogden is a retired Senior Technical Staff Member at the International Technical Support
Organization, Poughkeepsie. He enjoys working with new mainframe users and entry-level
systems.

Thanks to the following people for their contributions to this project:

Keith VanBenschoten, IBM Poughkeepsie, was very helpful in establishing installation and
startup processes for the 1090 and in providing test systems.

Theodore Bohizic, IBM Poughkeepsie, helped us understand command, design, and

internal details.

Richard Brandle, IBM Dallas, helped with much of the practical usage information
incorporated in this redbook.

Now you can become a published author, too!

Join us for a two- to six-week residency program! Help write a book dealing with specific
products or solutions, while getting hands-on experience with leading-edge technologies. You
will have the opportunity to team with IBM technical professionals, Business Partners, and
Clients.

© Copyright IBM Corp. 2009, 2011. All rights reserved. vii

 Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you
will develop a network of contacts in IBM development labs, and increase your productivity
and marketability.

Find out more about the residency program, browse the residency index, and apply online at:
ibm.com/redbooks/residencies.html

Comments welcome
Your comments are important to us!

We want our books to be as helpful as possible. Send us your comments about this book or
other IBM Redbooks publications in one of the following ways:
򐂰 Use the online Contact us review Redbooks form found at:
ibm.com/redbooks
򐂰 Send your comments in an e-mail to:
[email protected]
򐂰 Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. HYTD Mail Station P099
2455 South Road
Poughkeepsie, NY 12601-5400

Stay connected to IBM Redbooks

򐂰 Find us on Facebook:
http://www.facebook.com/IBMRedbooks
򐂰 Follow us on twitter:
http://twitter.com/ibmredbooks
򐂰 Look for us on LinkedIn:
http://www.linkedin.com/groups?home=&gid=2130806
򐂰 Explore new Redbooks publications, residencies, and workshops with the IBM Redbooks
weekly newsletter:
https://www.redbooks.ibm.com/Redbooks.nsf/subscribe?OpenForm
򐂰 Stay current on recent Redbooks publications with RSS Feeds:
http://www.redbooks.ibm.com/rss.html

viii IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 1

Chapter 1. Linux and 1090 installation

The 1090 operates as a normal Linux application. IBM support assumes certain patterns of
installation and usage. The “supported” bases for zPDT, both hardware and software, are
described in Volume 1 of this series of documents.

We strongly recommend that the general procedures described here be followed for initial
1090 usage. After you have gained some experience with the 1090, you can explore other
installation and usage arrangements. Many of our choices are arbitrary and simply reflect our
preference for a simple Linux.

Note: This document mentions both 32-bit and 64-bit versions of zPDT. The 32-bit
versions are for IBM internal use only. The 32-bit version is “stabilized” and support will be
dropped in late 2011.

We assume the PC is dedicated to Linux, with the 1090 application used when wanted. If this
is not the case, we suggest obtaining a separate hard disk for the Linux disk if this is possible.
The original hard disk can then be used for its original purpose. If this is not appropriate, then
a dual boot environment might be created. There are so many variations possible that we do
not attempt to provide specific instructions for creating dual boot installations. You should
ensure that sufficient free disk space is available for Linux and your emulated System z
volumes. For Linux and a very small z/OS you should have at least 40 GB of free disk space.

Virtual environments, such as with VMware, Xen, or KVM or similar product environments,
are not supported. Informal attempts to use these environments have not always been
satisfactory. The fundamental issue is that zPDT, with z/OS running under it for example, is a
large, heavy, complex environment that pretty much consumes the PC running it. It also
introduces timing constraints (for the many timers that z/OS has running internally) that do not
fit well in an extended virtual environment. Successful users of these virtual environments
have ample hardware resources, especially memory.

For some examples, we elected to install Linux with fixed IP addresses, with firewalls and
other security elements disabled. This was to ease communication in a private LAN
environment (connected to a small, personal router). Your needs may be different. The 1090
functions are not related to these controls, except that you may need to open firewall access

© Copyright IBM Corp. 2009, 2011. All rights reserved. 1

 for TCP/IP connections to the 1090 functions. A number of different LAN and TCP/IP
configurations are explored in Chapter 3, “LANs and TCP/IP” on page 27.

Ordering requirements
This document does not provide detailed ordering information for zPDT. The ordering process
may differ for various categories of users and for different countries. Whatever ordering
process is used should result in the following:
򐂰 One of the 1090-supported Linux distributions (current versions of Red Hat Enterprise
Linux (RHEL) or Fedora, or Novell SUSE Linux Enterprise Server (SLES) or openSUSE.
This may need to be ordered, or it might be downloaded from a website. It is not supplied
by IBM.
򐂰 A 1090 token (which may need to be activated via an IBM business partner, 1090 supplier,
or through IBM ResourceLink).
򐂰 The 1090 software, which must be installed before the token can be activated (if it is not
supplied already activated). The 1090 software does not include any System z operating
systems.
򐂰 Whatever System z software you plan to use, in a format usable with the 1090. This may
require a different ordering process than ordering the 1090 itself. The remainder of this
document assumes you have acquired the z/OS AD-CD package to use with your 1090.

Much of the material in this document assumes that you will install the z/OS AD-CD system. If
you are installing different System z software, you need to obtain specific instructions for the
1090 from the supplier of that software.

Installation overview
A summary of the usual installation sequence is this:
1. Read this series of books. You may not remember all the details at this stage, but you
should skim through most of the material before starting. Remember to work as root when
indicated and as another userid (ibmsys1 in all our examples) when indicated. If you are
new to Linux or the 1090, install a simple system first, before attempting something more
complex. Do not use root for installation and operation actions.
2. Think about your disk partitioning, especially if you plan to install major applications in
addition to the 1090 package.
3. Gather the required software packages:
– Linux for your base PC. Be certain that you have the correct Linux (32- or 64-bit
version). zPDT checks for Red Hat or SUSE indicators and will not install with other
Linux distributions.1
– The 1090 software (which might be obtained on a CD or DVD, or by a download).
• Two prerequisite modules, the 1090 modules, and the license agreement are all in a
single (non-rpm) file. There are two of these files, one for 32-bit environments and
one for 64-bit environments. Each of these files contains both the Red Hat and
SUSE versions of the 1090 code. The proper version is automatically installed on
your system.
• Your System z software (z/OS, z/VM®, or z/VSE™) in a format usable with the
1090.
4. Follow the installation steps described later in this chapter:
a. Install Linux. See the notes below << what notes??>>for suggestions.

1
The 1090 installation program checks the base Linux system for Red Hat or SUSE indicators. It is possible that
other distributions may have one of these indicators, allowing 1090 installation to proceed.

2 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 b. Install x3270 (or another 3270 emulator) if it is not included in your base Linux
distribution. Optionally, customize the x3270 keyboard.
c. Create group zpdt and userid ibmsys1.2
d. Install the 1090 package.
e. Customize several Linux files (sysctl.conf, /etc/profile.local, /etc/profile, and
.bashrc).
f. Copy or create a devmap.
5. Activate your 1090 token if necessary, as described in 1.5, “1090 hardware key activation”
on page 14. You cannot do this until the 1090 package is installed. (This step may be done
by a business partner or 1090 service provider.)
6. Generally following Chapter 3, “LANs and TCP/IP” on page 27, install z/OS or other
System z software:
a. Select the AD-CD distribution (or another System z operating system)
b. Unzip the volumes.
c. Customize or create a devmap.
d. Start the 1090 and IPL your operating system.
7. After you have run a basic system, you might consider LAN configurations.

As is often true with new hardware and software combinations, remember that a given Linux
level may not support the newest PC hardware. This is most often seen with new LAN adapter
chips and with new graphics chips and/or display panels. Support for these may require
additional Linux drivers or upgrades. If you have a very new PC model, or an unusual
configuration, you may need to verify that your Linux version is completely operational on your
hardware.

1.1 Disk planning

During Linux installations we usually create three partitions on the hard disk:
򐂰 A root partition for Linux (including the various 1090 files)
For a typical laptop, we usually make this about 10-20 GB although this is larger than
routinely needed.3 This partition contains all the normal Linux root directories, such as
/usr, /lib, /home, /etc, and so forth. If you have additional major applications installed
(other than basic Linux functions), this partition may need to be much larger.
򐂰 A swap partition for Linux. We suggest 4 GB (or larger)
Small Linux systems in a 32-bit environment seem to work well with a 2 GB swap partition.
Larger Linux systems should have a larger swap partition. A common recommendation is
(real memory size) + 2 GB, although this may result in some wasted disk space.
򐂰 A large partition for emulated System z volumes
We mount this partition as /z. We normally use all the remaining space on the disk drive
for this partition.

If you create a separate /home file system, it should be large enough for several sizeable core
image files. At least several gigabytes are suggested.

2
This is not required. However, all our examples assume that the 1090 is operated through Linux userid ibmsys1.
Whatever userid is used must be no longer than eight characters. Do not attempt to operate the 1090 while working
as root.
3
A machine with larger memory will typically have a larger Linux file system. Among other things, it should be able to
hold one or more core image files that may be created in unusual situations. A core image file created under zPDT
might be somewhat larger than the System z size defined in the devmap.

Chapter 1. Linux and 1090 installation 3

 This disk usage layout is not required. You could make many partitions for the various
standard Linux directories. You could place emulated volumes in various directories under
/home. You could place emulated volumes in /tmp, and so forth. We recommend our disk
layout as a starting point solely because it is simple and it isolates emulated System z
volumes from the normal Linux files. This isolation is useful if you reinstall Linux (without
disturbing your emulated volumes) and it may have minor performance benefits because it
tends to reduce fragmentation in the disk space used for large emulated volumes.

If you plan a dual boot system, then you will have at least one more partition (probably for
Windows). You will probably need to shrink the existing Windows partition to make room for
the new partitions. The various ways to do this are not covered in this document.

1.2 Linux installation

Install your Linux distribution. You might select only those packages that are needed for basic
Linux operation, or you might install everything in your distribution. We make the following
suggestions:
򐂰 Select Universal Time (UTC) for your base PC, if this is possible. (This may not be
possible if you also run Windows on the same PC. Do not consider changing the PC
time-of-day when switching between Linux and Windows; this can disrupt your zPDT
usage.)
򐂰 While not a Linux option, machine hiperthreading (if available) must be disabled at the
BIOS level. The z1090 cannot use a machine with hiperthreading.
򐂰 Include 32-bit support, which is an option during Linux installation. It is required for the
1090 token drivers.
򐂰 For Red Hat releases we recommend including the dmidecode rpm. For SUSE releases
we recommend including pmtools. Both packages include the upddecode tool. These are
optional, but they might be used to provide additional diagnostic information if there is a
problem with zPDT. If they are not in your Linux distribution, do not worry about it.
򐂰 We use gnome as our desktop manager, and this is reflected in our examples. You could
select KDE (we have no indication that it would not work with zPDT).
򐂰 We recommend the k3b package for burning DVDs. It seems to adapt to more different
drive types than other packages.
򐂰 We avoid installing beagle, although it is sometimes difficult to avoid. This is an automatic
indexing tool that apparently tries to index almost all files, including System z emulated
volumes. We found that it consumed substantial processor time and slowed zPDT
operation. This was noticed in earlier Linux releases, and this problem may not exist in
current releases.
򐂰 We usually install telnet-server if it is present in the Linux distribution, although this is an
insecure service. It is not necessary to use it, but it is convenient to have it installed if a
simple telnet session to the zPDT machine is needed. (All zPDT functions can be run
remotely, through telnet or ssh or other packages.)
򐂰 Install x3270 if it is included in your Linux distribution. It is not installed by default. You may
need to search diligently to find it, or to determine that it definitely is not present in your
Linux distribution. Generally, we find that the Linux installer provides a way to specify
installation packages at the rpm level, but some effort may be needed to find this path.
򐂰 Install vsftp or some other Linux ftp package. It is not needed for zPDT use, although you
may want to transfer files between Linux and z/OS using ftp.

4 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
򐂰 The X Software Development package, or something similar, may be needed if x3270 is
not included in the initial installation and is to be installed later.
򐂰 We have sometimes found it advisable to perform an online update for the Linux
distribution. If this is available for your Linux, we suggest you perform the update.
򐂰 Determine if additional drivers or driver updates are needed for your PC.
򐂰 You must manage whatever firewall and other security functions that you install with your
Linux. We suggest disabling any firewall when first working with the 1090 if you plan to
make external 3270 connections to it. Once you are familiar with 1090 operation, you can
reestablish the firewall functions. If you have external TCP/IP connections (for local 3270
connections, for OSA connections, or for CTC connections) you must provide appropriate
port holes in any firewall you use.

The following is an example of a simple Linux installation process on a W500 mobile

computer. This particular example was based on RHEL 5.3. The details are different for other
Linux distributions, but the concepts tend to remain the same. Many of our choices are
arbitrary.
(boot from DVD)
(The installer was unable to work in graphic mode on our particular mobile
computer)
Media test: <skip>
Language selection: English <OK>
Keyboard selection: US <OK>
Installation number: skip entering Installation Number <OK>
Partitioning type: Create custom layout <OK>
Device Start End Size Type Mount Point
/dev/sda
sda1 1 1084 8002M ext3 /
sda2 1085 1355 2000M swap
sda3 1356 25841 180775M ext3 /z
<OK>
Boot Loader Configuration: Use Grub <OK>
Boot Loader Configuration: <OK>
Boot Loader Configuration: (no password) <OK>
Boot Loader Configuration: boot label=Red Hat Enterprise... <OK>
Boot Loader Configuration: /dev/sda Master Boot Record (MBR) <OK>
Configure Network Interface: Yes
Configure Network Interface for eth0: Activate on boot
Enable IPv4 support <OK>
Configure Network Interface for eth0: Manual address configuration
IP=192.168.0.80 / 255.255.255.0 <OK>
Miscellaneous Network Settings: Gateway=192.168.0.1 <OK>
(no DNS specified)
Hostname Configuration: manual = W500 <OK>
Time zone: (as needed) (system clock uses UTC) <OK>
Root password: xxxxx (be certain to check the shift key first!)
Package Selection: Customize software selection <OK>
Administration tools
Development Libraries
Development Tools
Editors
Gnome Desktop Environment
Graphical Internet
Graphics
Legacy Network Server (optional: select telnet-server, inetd via F2)

Chapter 1. Linux and 1090 installation 5

 Legacy Software Support
Network Servers (this provides a VNC server)
Office / Productivity (optional)
Server Configuration Tools
Sound and Video
System Tools (do not select x3270 via F2)
Text-based Internet
X Software Development (needed for later x3270 installation)
X Window System
<OK>
Installation to begin: <OK> (takes a while to install packages)
Reboot: <OK>
Setup Agent: Authentication: Run Tool: Use MD5 passwords
Local authentication sufficient <next>
Setup Agent: Firewall Config: Run Tool: Security level disabled
SELinux disabled <OK>
<Exit>

At this point we were presented with a “teletype mode” (non-graphic) login. Our W500 mobile
computer high-resolution panel (1920x1200) was not recognized by our new Linux system. If
your system enters a normal graphic mode, the following steps are not needed.
login: root
# init 5 switch to graphics mode
(screen blinks several times)
Failed to start the X server ....
Like to view error details...? <No>
Like to try to configure X server...? <Yes>
(several messages, pauses, blinks)
Display settings Resolution 800x600 (no other useful choices available)
Display Settings changed <OK>
Trying to restart the X Server <OK>
(blinks several times. Should then switch to full resolution)
# gedit /etc/inittab
find line: id:3:initdefault:
change to: id:5:initdefault:

As noted in the script above, we suggest you disable SELinux (“SEL”) for initial 1090 usage, or
set it to permissive. Otherwise, you may have permission problems when starting the 1090,
with messages such as the following:4
/usr/z1090/bin/libhmc_s.so: cannot restore segment prot after reloc: Permission
denied

TN3270e clients
IBM has used these TN3270e clients with the 1090 offering:
򐂰 x3270 (recent versions)
򐂰 Recent PCOM releases (running on Windows systems)
򐂰 PowerTerm with the IBM Open Client system

We most commonly use x3270. Our last step in the Linux installation we are describing was
to install x3270, since it was not included with most current Linux distributions.5 An x3270
package is usually a single rpm, although we needed two packages as part of a particular

4
We experienced this with RHEL 5.2. We did not try running RHEL 5.3 with SELinux enabled.
5 An exception is SLES 11, which includes x3270.

6 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 x3270 we used in one case. (The two rpm packages were obtained by downloading them
from the web.) The two packages, in the order they must be installed, were:
x3270-3.3.4p7-3.e15.1.i386.rpm (not needed with some x3270s)
x3270-x11-3.3.4p7-3.e15.1.i386.rpm6

Other x3270 levels may be used, or another 3270 emulator may be used. In order to install
these two rpms, we found it was necessary to include the X Software Development package
when we installed RHEL 5.3 Linux. Note that this particular x3270 version did not include the
keyboard map file we describe next.

1.2.1 x3270 keyboard maps

The default x3270 keyboard assignments are not in the traditional 3270 style. In particular,
the large Enter key on the PC keyboard functions as the 3270 Enter key. With traditional 3270
keyboards this same key provides a new line function and the 3270 Enter key is located
where the right-hand Ctrl key is located on most PC keyboards.

There is no requirement to change the default x3270 keyboard mapping. If you prefer the
more traditional mapping, use the following steps (working as root):7
# cd /usr/share/X11/app-defaults

This directory may contain file X3270 (with an upper case letter X). Use the appropriate path
to app-defaults for your Linux and verify that file X3270 is present. If it is not present, you
could consider using a local x3270 profile, described later.
# gedit X3270 (use your favorite editor)
(scroll to the stanza named X3270.keymap.base.3270: #override)
(scroll to second line in this stanza):
...
Shift<Key>Return: Newline()\n\
:<Key>Return: Enter()\n\ <-- delete this line
:<Key>Linefeed: Newline()\n\ <-- delete this line
:<Key>Backspace: Erase()\n\ <-- delete thisline
<Key>Control_R: Enter()\n\ <-- add these lines
<Key>Control_L: Reset()\n\
<Key>Return: Newline()\n\
<Key>Pause: Clear()\n\
<Key>BackSpace: BackSpace() Delete()\n\
<Key>KP_Enter: Enter()\n\ <---optional
<Key>End: EraseEOF()\n\ <-- optional
<Key>Prior: PF(7)\n\ <-- optional
<Key>Next: PF(8)\n\ <-- optional
Shift<Key>Tab: BackTab()\n\
...

Notice that the 3270 screen defaults to model 4 (with 43 lines). Our ThinkPad keyboard
contained extra keys associated with Microsoft Windows usage, making the left and right Ctrl
keys smaller than they are on some keyboards. We did not attempt to map these Windows
keys to any 3270 function.

As a result of these changes to the keymap, common 3270 functions are as follows:

6 Some x3270 implementations do not use this second rpm.

7
Do not place any blank lines, tab characters, or extra blanks at the end of the lines within these definitions! The
X3270 file appears to be very sensitive to unexpected characters within the definitions. Some Linux distributions do
not contain this file and customizing x3270 for these distributions can be more challenging.

Chapter 1. Linux and 1090 installation 7

 Function Key
3270 Enter Right-hand Ctrl key or the numeric keypad Enter key
3270 Reset Left-hand Ctrl key or alt-r
3270 Clear Pause or alt-c
Next line Large Enter key on keyboard
PA1 alt-1
PA2 alt-2
F13 shift-1

You can adapt these instructions to other x3270 versions or simply use the default keymap
distributed with x3270.

Local x3270 profile

An alternative to changing the app-defaults/X3270 keyboard map (or if this file does not exist)
is to override the x3270 default keyboard using a profile in your home directory. To do this,
create a file (in your home directory) named .x3270pro (note the period as the first character
of the file name):
! Use Bill’s overrides
x3270.keymap: bill
! Define the overrides
x3270.keymap.bill: #override \
<Key>Control_R: Enter()\n\
<Key>Control_L: Reset()\n\
<Key>Return: Newline()\n\
<Key>Pause: Clear()\n\
<Key>BackSpace: BackSpace() Delete()

It seems that x3270 keyboard files are very sensitive to extra spaces and tab characters. Do
not have anything after the \n\ in the text lines. In this file, we spaced the <Key> field starting
in column 4, although this was arbitrary.

x3270 fonts
If x3270 is installed from a separate source, it may not have its normal fonts. In the x3270
fonts menu there may be an option for iso fonts. We selected the following one:
-eti-fixed-bold-r-normal--18-180-72-72-c-90-iso8859-1

The 18 that is embedded in the name is the point size. A similar choice, with 24 in this position
selected a larger font.

1.2.2 Other Linux notes

You should always use the same Linux userid for zPDT operation. This Linux userid must be
no longer than eight characters.8 Multiple zPDT instances, as described in the third book in
this series, require a different Linux userid for each instance.

We found the following Linux commands to be useful for setup verification:

$ ulimit -a (display various limits for this user session)
$ ipcs -l (lower-case l; shared memory limits)
$ /sbin/sysctl -a (many kernel and other system parameters)
$ /sbin/ifconfig (LAN status)

8
The Linux userid is used as the LPAR name under zPDT, and LPAR names are limited to eight characters or less.
(Only a subset of LPAR-like functions are provided by zPDT.)

8 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 Other Linux distributions
Linux distributions other than Red Hat and SUSE are not acceptable to the zPDT installation
process. “Force fitting” zPDT to other distributions may create obscure errors.

CD/DVD drive access

For the Linux distributions we used, the path used to access the CD/DVD drive is
/media/xxxxx where xxxxx is the volume name or title of the CD/DVD. Whoever creates a
CD/DVD can assign a title. You may be able to determine a CD/DVD title by observing the
window title that is presented when the Linux automount function detects the new CD.

Many of our examples use path /media/ROM to access the drive. This would be the correct
path for a CD/DVD with the title ROM. A CD/DVD with a different title would have a different
path name.

Linux PATH
We suggest that you do not add other directories before /usr/z1090/bin in the PATH and
LD_LIBRARY_PATH variables. There are many commands and executed modules provided
with the 1090 and these correspond to Linux file names that are accessed through the PATH
variables. For example, the command d is used to display System z memory. If you should
place another directory containing a file named d earlier in the PATH, then the 1090 d function
would not be available in the normal manner. Various internal 1090 functions assume they
can access 1090 modules via PATH and LD_LIBRARY_PATH; you must ensure that this is
possible.

1.3 Install the 1090

Decide on the Linux userid you wish to use for zPDT. We use ibmsys1 in all our examples, but
you can select any userid that is eight characters or less. We also create a Linux group
named zpdt and add userid ibmsys1 to it. A special group for the 1090 is not required, but it
can be used for additional security controls.9

Note that $ prompts (throughout the examples in this document) indicate a non-root userid
and # prompts indicate we are working as root. We recommend that you always log in as
ibmsys110 and then use an su command to switch to root when needed. The following
directions assume that a single 1090 instance will be used. (Multiple 1090 instances require
multiple userids, such as ibmsys2 and ibmsys3.)

If you have not already done so, create group zpdt and user ibmsys1, which should be a
member of group zpdt. (These specific names are not required; however, we use them
consistently in all documentation. Earlier documentation used group ibmsys instead of group
zpdt; the change is arbitrary.)

By default, userid ibmsys1 has /home/ibmsys1 as its home directory and most 1090 control
files appear in subdirectories here. We created file system /z as a separate partition during
our Linux installation.11 We want userid ibmsys1 to own this file system:
(log on as ibmuser1)
# su switch to root

9
The third volume contains a note about limiting access to the only zPDT module that involves running with root
authority.
10 There is nothing special about userid ibmsys1. We consistently use it to illustrate 1090 operation. Any userid with

8 or fewer characters can be substituted for ibmsys1, but that userid should be consistently used for all 1090
installation and operation actions.
11 This may not be the case for the IBM Open Client, but we ignore this exception here.

Chapter 1. Linux and 1090 installation 9

 # chown ibmsys1:zpdt /z user ibmsys1 to own emulated volume directory

You need a single executable file to install the 1090 base functions. There are two versions of
this file (for 32 or 64-bit environments) with names such as:
z1090-1-2.41.35.x86_64 (64-bit environments; verify your exact file name)
z1090-1-2.41.35.i586 (32-bit environments; verify your exact file name)

The single file contains the following:

򐂰 An sntl-sud rpm at the correct level (A driver for the 1090 token)
򐂰 An shk-server rpm at the correct level (Another token program)
򐂰 The primary z1090 rpm for SUSE
򐂰 The primary z1090 rpm for Red Hat
򐂰 An installer program that displays a license and then installs the rpms. The correct z1090
rpm (Red Hat or SUSE) is automatically selected for your base Linux system.

Proceed with 1090 installation as follows. The first goal is to move the installation file to a
convenient directory, such as /tmp. If you obtained the 1090 installation file via ftp or some
other dowload method, you may have already placed it in /tmp.
(log on as ibmsys1)
$ su (change to root)
# cd /media/ROM (if you install from a CD)12
# cp /media/ROM/z1090-1-2-41.35.x86_64 /tmp (use the correct name)
# cd /tmp (the file is in /tmp)

Execute the installer program, for example:13

# chmod u+x z1090-1-2.41.35.x86_64 (make file executable, if not already)
# ./z1090-1-2.41.35.x86_64 (verify the exact file name first)14

Scroll through the license and reply to the question about the license. The various rpms are
then installed automatically. The z1090 installer program does the following, removing older
versions of these programs as needed:
򐂰 Two prerequsite rpms are installed.
򐂰 The 1090 rpm is installed, mostly in /usr/z1090/bin.
򐂰 A set of man files is loaded into /usr/z1090/man.
򐂰 A UIMD service is installed.

The installation may be followed with several messages about “missing LSB tags and
overrides.” These messages may be ignored. There should be messages about starting the
UIMD service; see “1090 serial numbers” on page 13 for more details about UIMD.

Installer options
The installer program has three options. Using the file name in the example above:
# ./z1090-1-2.41.35.x86_64 --refresh (reinstall current zPDT level)
# ./z1090-1-2.41.35.x86_64 --refreshall (reinstall zPDT and prerequsites)
# ./z1090-1-2.41.35.x86_64 --remove (remove zPDT and prerequisites)

The prerequsites mentioned here are two rpms that are needed to access the USB token.

12
This example assumes that ROM is the title of the CD. You must determine the title of your CD.
13
If you are coming from an older release of the 1090 you may have multiple copies of sntl-sud or shk-server
installed and the installation step will fail. In this case, do the following:
# rpm -e z1090 (remove the old 1090 programs)
# rpm -e --allmatch sntl-sud (repeat for shk-server if necessary)
14 The “./” characters before the file name tell Linux to execute this file from the current directory.

10 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
1.3.1 Alter Linux files
You must update a few Linux files before you can use the 1090. The following commands add
lines to /etc/sysctl.conf.15 We indicate the use of gedit but you may use any suitable editor
(such as vi) to create these files or add the indicated lines.16 (We suggest that you do not
attempt to use vi unless you have a basic familiarity with it!)

Some Linux distributions already have acceptable values for shmmax, msgmnb, msgmax,
and core_uses_pid, but other distributions may need to have all these values set.
(Unfortunately, some newer Linux versions restrict the gedit editor such that it is not easily
usable when running as root. You may need to overcome this; one way is to change the
permissions or ownership of the target files, using the chmod or chown commands. We ignore
this detail in the following examples.)
# gedit /etc/sysctl.conf (the following lines should begin in column 1)
kernel.shmmax=2415919104 (2.4 GB for 32-bit kernels)
kernel.shmmax=18000000000 (17 GB or more for 64-bit kernels)
(Use only one of these shmmax lines)
kernel.core_pattern=core-%e-%p-%t
kernel.core_uses_pid=1
kernel.msgmni=512
kernel.msgmax=65536
kernel.msgmnb=65536
net.core.rmem_max=1048576 (if needed)
net.core.rmem_default=1048576
# /sbin/sysctl -p /etc/sysctl.conf

Notes for sysctl values

The shmmax values shown above (and you must select the appropriate one, depending on
whether you have a 32-bit or 64-bit Linux system) establish the maximum shared memory
that a user can request. All system z memory, plus several other 1090 work areas, are in
Linux shared memory. Another parameter, shmall, sets the total shared memory size of all
users. The value of shmall is specified in page sizes, which is usually 4096. The default value
of shmall is usually very large and acceptable.17 However, if you have multiple 1090
instances, all with large System z memory, you might exceed the default shmall value. If this
happens you need to include a parameter such as:
kernel.shmall=300000000

This would result in the total amount of shared memory, for all users, to be 300,000,000*4096.
This value should be greater than the number of 1090 instances times the System z memory
size for each instance plus about 10%. A number much larger than needed appears to do no
harm.

If your intended System z memory size is larger than approximately 16 GB, then you need to
make the kernel.shmmax value larger. A reasonable value would be about 10% larger than
the total System z memory that you specify.

15 Some versions of the IBM Open Client reset these values when maintenance is applied. If this happens, you
should again enter the values shown here and run /sbin/sysctl.
16
The 32-bit shmmax value shown should be used for 32-bit Linux systems. The value shown for 64-bit systems (the
value is approximately 17 GB) is suitable for most users. If you have more than, say, 16 GB of real memory and you
intend to define a System z configuration with more than about 16 GB then the shmmax value should be increased.
As a general rule, the shmmax value should be at least 500 MB larger than the total System z memory you define
(for all instances) but your defined System z memory should be about 500 MB less than the real memory in your
machine.
17
The default value on several distributions is 1,152,921,504,606,846,720, which is huge. However, on at least one
IBM internally-distributed Linux the default is much lower and may need to be adjusted.

Chapter 1. Linux and 1090 installation 11

 The kernel.msgmni number, specified as 512 above, may need to be larger if you have many
emulated I/O devices. The msgmax and msgmnb changes are not needed for some Linux
releases because these are the default settings. However, including these parameters in
sysctl.conf does no harm; the settings are needed for proper OSA operation.

The net.core parameters may be needed if Ethernet large frames are used. These seem to
do no harm, so you may always include them. In this context, any frame with more than 1500
bytes is considered large. (IBM has not tested large Ethernet frames, sometimes known as
jumbo frames, and does not formally support them for zPDT.)

Profiles
The following lines should be added to /etc/profile.local. If this file does not exist, you
should create it. (Some Linux distributions do not use this file, but its presence should not hurt
anything.)
# gedit /etc/profile.local (the following lines should begin in column 1)
ulimit -c unlimited
ulimit -d unlimited
ulimit -m unlimited (if you have more than 128 emulated I/O devices)
ulimit -v unlimited (if you have more than 128 emulated I/O devices)

# gedit /etc/profile
(Add the following line as the last line if not already present somewhere in the profile. It
is already present in many distributions.)
test -s /etc/profile.local && . /etc/profile.local

The ulimit commands in /etc/profile.local are not effective unless this file is processed
from the /etc/profile reference. The ulimit commands can also be placed in the .bashrc
file (or in both places).

Change from root to ibmsys1:

# exit (leave root)
$ cd /home/ibmsys1 (my login directory)
$ gedit .bashrc (use your favorite editor)
Add the following lines beginning in column 1):
export PATH=/usr/z1090/bin:$PATH
export LD_LIBRARY_PATH=/usr/z1090/bin:$LD_LIBRARY_PATH
export MANPATH=/usr/z1090/man:$MANPATH
ulimit -c unlimited
ulimit -d unlimited
ulimit -m unlimited (if more than 128 emulated I/O devices)
ulimit -v unlimited (if more than 128 emulated I/O devices)

Double-check the entries in all of these Linux files. Errors here may be difficult to detect later.
The ulimit -m and -v statements are not required for most users and should probably be
excluded unless you have more than 128 emulated I/O devices.)

Check your 1090 distribution materials to see if there are sample devmap files that may be
helpful.18 Copy these to /home/ibmsys1, for example:
$ cd /tmp/ROM (or wherever your 1090 source is))
$ cp aprof12 /home/ibmsys1/aprof12 (sample devmap)
$ chmod 664 /home/ibmsys1/aprof12

18 These might be provided by your zPDT service provider.

12 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 Note that any sample devmaps probably must be edited to match your configuration and file
names. If you do not find a sample devmap, you need to create one before you can start
zPDT.

You may also notice a new directory named /etc/z1090.d containing one or two small files.
These are part of the license (token) control process and should require no work.

Reboot Linux
Reboot Linux to pick up all the changes you have made. You should then use the
z1090instcheck command to partly verify your environment for running the 1090. Your new
PATH is needed to find the command:
(log in as ibmsys1)
$ z1090instcheck

If this command is not found, you do not have the PATH variables set or you did not install the
1090 code correctly. Note that this command does not check any devmaps that you may have
defined or copied.

1.4 1090 serial numbers

In the most basic case, the System z serial number is the same as the token serial number
(which is also printed on the token or token tag). Starting with the GA 2.2 release (June 2011)
the serial number of the token is stored in a Linux file. If a different token is used when the
1090 is started again, a warning message is produced; however, the 1090 will continue
operation in the normal way. The warning message is:
AWSEMI200W Current CPU serial number xxxxx does not match previous number yyyyy

If multiple tokens are used (at the same time), a specific System z serial number is assigned
and will be used consistently. (In earlier releases, the serial numbers from the multiple tokens
were used somewhat randomly.) The specific serial number is stored in the Linux file for reuse
on subsequent 1090 startups. This number (and other identifying numbers) are managed by
a 1090 service known as Unique Identifier Manager (UIMD).

When this 1090 release is installed, a new directory (/etc/z1090.d) is created. After the 1090
is started the first time, it will contain a file named uimd.db. The effective 1090 serial number
is contained in this file, along with some binary information. You should not edit this file, but
you may delete it. If you delete it then any previous serial number assignments are removed.
The file will be automatically created the next time you start a 1090 instance and the serial
number will be assigned from the token you use at that time. If multiple tokens are used, a
serial number is generated and saved for future use. (This avoids any randomness of serial
numbers when multiple tokens are used.)

The UIMD service may place a small log entry in /var/logs when Linux is booted. Such log
entries may be deleted if they become a problem. The UIMD service is started automatically
when Linux is booted and the operation should be automatic. In unusual situations, the
following Linux commands may be used to control it:
# service uimd start
# service uimd stop
# service uimd status
# service uimd restart

Chapter 1. Linux and 1090 installation 13

1.5 1090 hardware key activation

Note: At the time of writing, the material in this section (about token renewals) applies only
to tokens obtained through the early IBM PartnerWorld® channels or the IBM internal RPQ
process. It does not apply to tokens obtained through other channels.

A USB hardware key (token) is valid for a year from the time it was last activated.19 Activation
(and lease renewal) may be handled by your zPDT service provider (such as an IBM
Business Partner) or by using IBM Resource Link™ in some cases. IBM Resource Link
usage for token activation requires an IBM employee userid or a userid that has been added
to a list of certain zPDT token users. Your 1090 provider should have information about this.

1.5.1 IBM Resource Link

Instructions are provided with the 1090 USB hardware key (token) for initial activation and
renewals using Resource Link (if appropriate). For convenience, we include a summary here.

The important steps in this process are summarized as follows:

1. Preliminary work.
– Obtain a suitable Resource Link ID (profile)20 and password.21
– Copy and save the information printed on the tag attached to your token.
2. Install the 1090 software on your Linux machine, as described earlier in this chapter. The
installation can be done without using the token. (You need a working token to run the
1090 software.)
3. Connect your token to a USB port (on your 1090 machine) and run the 1090
SecureUpdateUtility program to create a request file.
4. Using any PC connected to the Internet, log on to Resource Link and send the request file.
The details for doing this are described below.
5. After a while you will receive an e-mail with an attached update file.22
6. Run the 1090 SecureUpdateUtility program to apply the update file to your token.
7. Your token is now ready to use. You will need to repeat the process after a year (or any
time before a year expires).

If your 1090 Linux system is connected to the Internet you can perform the whole process
from there. In practice, we find many 1090 systems are not connected to the Internet. In this
case, you can copy the request file and the update file between your 1090 machine and your
Internet machine (possibly running Microsoft Windows) by using a memory stick, a diskette,
FTP, or any other convenient method. These two files are small.

An update file functions only with the specific token that you identified in the request file, and
can be used only once.
19 This was true at the time of writing. Future availability plans may manage this in a different way.
20
Also known as an IBM Registration ID. If there is a problem send a note to [email protected] to request help
with Resource Link registration.
21 For IBM internal use, this Resource Link userid must be an IBM employee userid. For certain other users, it must

correspond to the user that is registered for 1090 usage.

22
The Resource Link function also provides a Web page where the upw file can be downloaded. Providing the Web
page takes a little time and it may not be ready as quickly as you receive the e-mail response. The upw is the same
in both the e-mail and Web options, and you may use the most convenient way to receive the upw file. The Web
option is convenient if your 1090 system is connected to the Web, and if it is not your e-mail system (thus avoiding
any e-mail requirement).

14 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
Preliminary work
Copy the information that is printed on the token tag (illustrated in Figure 1-1) attached to the
USB hardware key. Save this information in a safe place.

11S number: use last 6

digits (055123 in this example) (11S)PN/SN: 15r7312 YH1102055123
|| |||| ||||| || || |||| || |||| N79

Type 1090-L01
S/N 02-1180C

MTSN number: Canada iCES/NMB-003 IBM-1090-XXX(A)

Class/Classe A FCC class A - see manual
(02-1180C in this example)
Figure 1-1 USB hardware key tag

The data in the 11S and MTSN fields on the tag is required to:
򐂰 Activate the USB hardware key for the first time.
򐂰 Extend the lease for one year.
򐂰 Activate and use a replacement USB hardware key.

A Resource Link profile (userid) is needed. This may be an IBM employee profile or a
PWD-approved profile for other users. If you do not have one, go to
http://www.ibm.com/servers/resourcelink

and follow the Register for an IBM ID link (in the upper right part of the panel). After
establishing a userid and password, follow the Sign in link to create your Resource Link
profile. Wait two hours after creating the profile before signing back in. The profile information
must be replicated among several servers, which can take some time.

PWD members must validate this userid with the IBM PWD office. If you do not have an IBM
employee Resource Link userid, or if your PWD Resource Link userid has not been validated
by the IBM PWD office, you will not see the appropriate menu items in Resource Link.

Activation (or renewal, date extension, or lease extension)

After this preliminary work, the key can be activated, renewed, or have the lease date
extended (these are all provided in the same way):
1. Connect the USB hardware key to your 1090 system, using any USB port. (You must have
already installed the 1090 software.)
2. Working as root, create a request file using the Secure Update Utility:
(log in with a normal z1090 userid, such as ibmsys1)
$ SecureUpdateUtility -r
Enter file name: myrequest (file name is arbitrary)
3. If necessary, move this request file to the computer used to access Resource Link and log
on to Resource Link. (The file name will have .req added as the name extension.)
4. On Resource Link, navigate to Tools  1090 Support  Date Extension and enter the
data from your hardware key tag. Use the last six digits of the 11S field. The serial number
(the MTSN field) can be entered with or without the dash; it is not case sensitive. Enter the
file name of your request file. Finally, click Submit.
5. Resource Link will create an update file and send it to you by e-mail. (This typically takes
about 10 minutes.) Receive this file and move it to your 1090 machine, if necessary. The
file name will be the same name that you sent, but with .upw as the name extension.

Chapter 1. Linux and 1090 installation 15

 6. Apply the file to the USB hardware key:
$ SecureUpdateUtility -u myrequest.upw
7. After the Secure Update is successfully applied, unplug the USB hardware key. Wait at
least 10 seconds and then reconnect the hardware key. It is now ready for routine 1090
operation.

1.6 Installing a new 1090 release

New 1090 releases are typically available through your Business Partner or (for IBMers and
PWD members) through Resource Link. The installation procedure is the same regardless of
the source. Installation is exactly the same as described earlier.

A summary of the steps is as follows:

1. Obtain the new distribution file, taking care to obtain the desired version (32-bit or 64-bit).
2. Working as root, execute the distributed file.

16 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 2

Chapter 2. AD CD z/OS installation

The System z Personal Development Tool provides System z CP functionality and associated
utility programs. It does not include any System z software. System z software, including
operating systems, utilities, middleware, applications, and so forth, must be obtained
separately.

For software licensing purposes, a 1090 system is a System z and all software licensing
requirements that apply to a larger System z installation also apply to a 1090 installation. This
statement applies to all System z software from IBM and, we assume, applies to all System z
software available from other vendors.1

The discussions in this chapter (and elsewhere in this series) assume that proper licenses
have been obtained for the System z software. Licensing arrangements (and associated
costs) can be complex topics and are not further addressed in this document.

Important: The discussions in the remainder of this document and in the third volume in
this series assume the reader has a general familiarity with z/OS systems programming
and understands how to access various control data sets. We highlight specific details that
may be relevant to 1090 usage and the current AD-CD releases. This is not intended as an
introduction to z/OS administration.

Furthermore, we assume basic familiarity with the AD-CD z/OS package. Update
information about the AD-CD packages may be found on:
http://dtsc.dfw.ibm.com

1
In this discussion we include software for zSeries®, S/390s, and so forth, in the general category of System z
software.

© Copyright IBM Corp. 2009, 2011. All rights reserved. 17

2.1 General principles
All current IBM System z operating systems (assuming proper licenses exist) are supported
for 1090 usage. This includes current versions of z/OS, z/VM, and z/VSE. Linux distributions
intended for System z usage may be used, but all functions and configurations have not been
extensively tested. Older versions of operating systems and other software may work
correctly (provided they are at least at the XA level), but there is no formal testing or support
for older software.

Software installation methods may be different for 1090 systems than for traditional System z
installations. This difference is due to the differences in I/O devices available on 1090
systems and on larger System z machines.

2.2 System z operating systems

There are specific limitations for installing IBM operating systems. These limitations are
related to the use of the software media and packaging techniques involved and are not
limitations on the use of the operating systems, once they are installed.

The most common limitation is for software that is distributed on tape. To install this software,
your 1090 must have a tape drive and these are not commonly available for PC machines.
Another limitation is related to any System z software that is packaged in such a way that
installation requires specific System z HMC functions.

Other considerations may be important for specific middleware or applications. For example,
the largest System z memory that can be emulated with a 32-bit version of the 1090 is
approximately 2 GB. That is, the System z operating system thinks it has up to 2 GB of real
memory. Software requiring more than this may not be practical. Some software requires
hardware adapters that are not available with the 1090.

2.2.1 Media
In most cases (when a tape drive is not available) installation media is limited to CD, DVD, and
LAN connections. (We can consider FTP as “media” in this context.) CD or DVD files must be
in formats that can be processed for the 1090. There are two meaningful formats:
򐂰 A Linux image of an emulated 3390 drive2 that can be restored in the 3390 format used by
the 1090; the image might be compressed (using gzip, for example) and would need to be
uncompressed before use by the 1090. Likewise, the image might be in tar files and would
need to be untarred (and possibly uncompressed) before being used by the 1090.
The 3390 drive image format must be produced by another 1090 system, because no
other product uses the same 3390 image format that is used by the 1090. Whatever
preliminary unpacking/uncompression is needed must be done by Linux utilities before the
3390 image can be used by a System z operating system.
򐂰 A tape image in awstape format; such images appear as “real” tape volumes to System z
operating systems, and can be processed as such by using emulated tape drives. The
tape might contain product installation material (in SMP/E format, for example), an
ADRDSSU dump of a disk volume, or any other tape data usable by System z programs.

2 3380 images could also be used, but we ignore these here.

18 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 The same files, in the formats described, could be exchanged by FTP (to the base Linux of
the 1090 system) instead of using CD or DVDs. This would not affect the processing
requirements.

Another media option is to FTP a product (or other data) directly to z/OS. Some System z
software is distributed in this format. Of course, the 1090 must have a running z/OS and LAN
connection in order to use this method. (Most of our discussion is for z/OS but z/VM, z/VSE,
or Linux for System z might be used in the same way. The point is that a working System z
operating system must be installed before additional software can be sent directly to it via
FTP.)

It is important to differentiate the handling of these methods:

򐂰 CDs and DVDs must be processed by Linux programs (unless they contain awstape files).
򐂰 awstape files must be processed by z/OS (or another System z operating system),
although the transport of awstape files can be managed by Linux through CD/DVDs or
FTP.
򐂰 Direct FTPs to z/OS may be in other formats, for example in formats suitable for
processing by SMP/E or the TSO XMIT command. In any event, these are System z
formats and not Linux formats.
򐂰 An emulated 3390 volume (after decompression, if necessary) is a large Linux file that is
meaningful only to System z software.

2.3 Packages for the 1090

At the time of writing, organizations within IBM produce one z/OS package that can be
directly installed on 1090 systems. This is the Application Development System (the AD-CD
System).3 It is distributed on DVDs, although parts may be obtained via downloads.

This package is not part of the IBM System z Personal Development Tool. It is a convenience
package for users of this tool. It is a z/OS system, with additional System z software products,
and requires appropriate System z software licenses for use. The AD-CD system is intended
for use by members of the IBM PartnerWorld for Developers, among other users.

An informal package for z/VM may be available. One of the standard z/VSE formats (based
on awstape files on a DVD) may be used. Brief descriptions of z/VM and z/VSE installation
processes are in Volume 3 of this series.

2.4 Installing an AD-CD system

The following examples use volsers corresponding to the z/OS 1.12 (January 2011) release
of the AD-CD system. These volsers tend to change in a standard pattern for new releases.

2.4.1 Specific installation instructions

There are typically at least four or five DVDs for a z/OS AD-CD release. The first DVD
contains the 3390 volumes needed to IPL and to use common subsystems. It may also
contain a README file, sample devmap, and so forth. The second DVD may contain DLIB
volumes. Additional DVDs may contain optional volumes for DB2®, WebSphere® Application

3 This is also known as the AD-CD system, where CD means Controlled Distribution.

Chapter 2. AD CD z/OS installation 19

 Server, and other material. Documentation with each AD-CD release contains specific
information about the DVD layout for that release.

The distributed emulated volumes are all in gzipped format. The z/OS 1.12 AD-CD system
uses DVD titles such as DVD1 ADCD1; again, we stress that you must determine the volume
title on your DVDs. (Some CD titles containing multiple blanks are difficult to use with a cd
command. We used the Linux automatic command completion function with these.) For
example:
(mount the first AD-CD DVD)
$ cd /media (DVDs are mounted as /media/xxxx)
$ cd ADCD_DVD1

AD-CD system installation might be as follows, assuming our target directory for emulated
3390 volumes is /z:
(work as userid ibmsys1)
$ cd /media/ADCD_DVD1
$ gunzip -c zcres1.gz > /z/ZCRES1 unzip volumes
$ gunzip -c zcres2.gz > /z/ZCRES2
$ gunzip -c zcsys1.gz > /z/ZCSYS1
And so forth for all the volumes to be installed.

We elected to use the volser of the 3390 volume as the Linux file name that holds the volume.
We use upper case letters simply to make these emulated volume file names more distinctive.
There is no requirement to use the volser as the Linux file name, and there is no requirement
to use upper case names.

The files containing emulated volumes (and the directory containing these files) must have
read and write permissions for the userid running the 1090 function. Assuming use of the
ibmsys1 userid, we suggest that all such files and their directories (/z in our examples)
should be owned by ibmsys1.

2.4.2 IODF device numbers

We must know the device numbers (“addresses”) used by the AD system. (These may be
changed after the z/OS system is running. Changing involves creating a new IODF data set,
new IPLPARM member(s), and re-IPLing z/OS.) Most users of the AD system accept the
device numbers generated in the IODF supplied with the AD system. These are as follows:
ADDRESS DEVICE Purpose
00C 2540R Card reader. Useful as an emulated device.
00E-00F 1403-N1 Line printers. Useful as an emulated device.
120-15F 3380 Disks. (Control units defined for 120-127)
300-318 3390 3390 disks
400-40F OSA OSA
550-55F 3400 Round tape drives
560-56F 3480 Without COMPACT feature
580-58F 3490 Tape drives
590-59F 3590 Tape drives
700 3270 Terminal. AD systems use as NIP & z/OS master console
701-73F 3277 Terminal. Normally for VTAM (TSO, CICS, etc)
900-907 3277 Terminal. Normally for VTAM (TSO, CICS, etc)
908 3270
909-91F 3277 Terminal. Normally for VTAM (TSO, CICS, etc)
A80-AEF 3390 Disks
E20-E23 CTC Typically for 3172s that appear as CTC devices

20 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 E40-E43 CTC Typically for 3172s that appear as CTC devices

These addresses are all three hex digits. This is due to historical reasons. Both the AD-CD
system and the 1090 system can work with four-digit addresses.

In principle the 3390 IPL volume, for example, could be mounted at any address in the
300-318 or A80-AEF range. In practice, the following addresses are typical:
VOLSER ADDRESS Purpose
ZCRES1 A80 IPL volume and key z/OS libraries
ZCRES2 A81 More z/OS libraries
ZCSYS1 A82 Paging, spool space, LOGGER data sets, VSAM, etc
ZCUSS1 A83 Data sets of UNIX System Services
ZCPRD1 A84 Additional program products
ZCPRD2 A85 Additional program products
ZCPRD3 A86 Additional program products
ZCDIS1 A87 Distribution libraries (optional)
ZCDIS2 A88 Distribution libraries (optional)
ZCDIS3 A89 Distribution libraries (optional)
ZCDIS4 A8A Distribution libraries (optional)
ZCDIS5 A8B Distribution libraries (optional)
ZCDIS6 A8C Distribution libraries (optional)
ZCDB91 A8D DB2 operational libraries
(And so forth, for whatever AD-CD volumes you want to use. The addresses need not be
sequential but must be in the 3390 ranges as defined in the IODF.)
SARES1 AA0 Single-volume z/OS (can be any 3390 address)

700 3270 for z/OS console

701-70F 3270 terminals for TSO, CICS, etc
400-40F OSA LAN connections in QDIO mode
E20-E21 OSA LAN connection in non-QDIO mode

These addresses and volsers may change in future AD-CD systems but the general pattern is
likely to remain the same. Additional 3390 volumes (for WebSphere Application Server or
local data, for example) are typically started at address A9x. These addresses are in the
ranges defined for 3390 volumes in the default IODF. Other than that, there is nothing special
about these addresses. For example, if you elect not to install the DLIB volumes, you might
assign a ZCDB91 volume to address A87; or you could leave it at a higher address and have
a gap in your addresses.

2.4.3 1090 control files

Before the AD-CD system can be used, the appropriate devmap must be created. A basic
example would be as follows:
$ cd /home/ibmsys1
$ gedit aprof12 (this is an arbitrary file name)
[system]
memory 2000m # define 2000 MB System z
processors 1 # use 2 or 3, if appropriate
3270port 3270 # port number for TN3270 connections

[manager]
name aws3274 0002 # define a few 3270 terminals
device 0700 3279 3274 mstcon
device 0701 3279 3274 tso

Chapter 2. AD CD z/OS installation 21

 device 0702 3279 3274 tso
device 0703 3279 3274 tso
device 0704 3279 3274 tso

[manager]
name awsckd 0001
device 0a80 3390 3990 /z/ZCRES1
device 0a81 3390 3990 /z/ZCRES2
device 0a82 3390 3990 /z/ZCSYS1
device 0a83 3390 3990 /z/ZCUSS1
device 0a84 3390 3990 /z/ZCPRD1
device 0a85 3390 3990 /z/ZCPRD2
device 0a86 3390 3990 /z/ZCPRD3
#(continue with whatever additional volumes you installed.)

Only the first four volumes of the AD z/OS 1.12 system are needed to IPL. However, the next
three volumes in the above list (ZCPRDx) are needed for common purposes and we suggest
that they always be installed. Gaps in the assigned address numbers do not create a
problem. The devmap can have any name and be placed in any directory. It is best if it is in
the directory you will use when starting the 1090 so that you do not need to enter a full path
name when using it.

The processors statement determines how many System z CPs are started for this 1090
instance.

We suggest you do not define OSA devices for your initial z/OS startup. The OSA definitions
can be a little more complex and we suggest you verify that your basic z/OS system is
operational first.

2.4.4 IPL and operation

Start the 1090 with an awsstart command. Among other functions this starts the 1090 device
manager that emulates local, channel-attached 3270 terminals. Using the awsstart
command creates a z1090 subdirectory in the current home directory (if it does not already
exist) and a number of zPDT-related directories below it.
$ cd /home/ibmsys1
$ awsstart aprof12 use your devmap name
(wait for messages. Press Enter to regain the $ prompt.)
AWSSTA014I Map file name specified: aprof11
0 Snapdump incident(s), RAS trace and RAS log files occupy 657046 bytes
in /home/ibmsys1/z1090/logs.
Associated files, logs, and core files occupy 10364 bytes in
/home/ibmsys1/z1090/logs

Using the same Linux window (or a different window, if you prefer) start at least two local 3270
sessions:
$ x3270 -port 3270 mstcon@localhost &
$ x3270 -port 3270 localhost &
$ x3270 localhost:3270 & (another way to specify a port number)
򐂰 x3270 is the name of the program
򐂰 We assigned Linux TCP/IP port 3270 for this function. This is specified in the devmap. The
port number is arbitrary, but should not be used for any other purpose in your system. Port
3270 is usually a good choice and is easy to remember.

22 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 򐂰 We want to connect to our own Linux system; this is indicated by the localhost operand.
The mstcon and TSO operands are the LUnames of the sessions and must match names in
the 3270 device statements in the devmap. These names are case sensitive. If no
LUname is specified, the next unused device for the aws3270 device manager is taken.
򐂰 The ampersand (&) causes the x3270 program to execute in the background, leaving the
Linux window free for additional commands. We can recall and execute the x3270
command repeatedly to create multiple 3270 sessions.

The 3270 window will display identification lines if there has been no data sent to it by the
System z software. These lines indicate the terminal identity by address and LUname or IP
address. A number of options are available for working with these LUnames and these are
discussed in volume 1 of this series. The File and Options menus at the top of the x3270
window can be used for a variety of functions. Changing the font size (using the Options
menu) has the effect of changing the 3270 window size.

The 3270 session for the z/OS console (address 700 for the AD-CD system) should be ready
before IPLing z/OS. Next issue the appropriate IPL command in the Linux window:
$ ipl a80 parm 0a82cs

After a few seconds, the initial z/OS messages should appear on the 3270 session at address
700. During the first IPL of the AD-CD system (or an IPL after a long period of non-usage) you
may see messages similar to the following:
IXC420D REPLY I TO INITIALIZE SYSPLEX ADCDPL, OR R TO REINITIALIZE XCF

If this message occurs, go to the 3270 session displaying the message and enter:
r 00,i

After VTAM® is started, the VTAM logo should appear on the other 3270 session.4

There is usually a writeup for each AD-CD release that provides details about different IPL
parameters and TSO logon procedures. A very brief summary for the z/OS 1.11 AD-CD
system is as follows:
IPLparm LogonProcedure Purpose
0A82CS ISPFPROC Basic IPL without DB2, etc. Cold start JES, CLPA
0A8200 ISPFPROC Subsequent basic IPLs. Warm start.
0A829C DBSPROC9 Initial IPL for DB2 V9, etc
0A829W DBSPROC9 Subsequent IPLs for DB2 V9, etc

Userid IBMUSER is always present on z/OS and is typically used for initial TSO logons. The
password for IBMUSER should be published with any AD-CD documentation. It is typically
SYS1 or IBMUSER. If there are security concerns about your system, this initial password
should be changed as soon as possible.

2.4.5 Shutting down

z/OS should be shut down cleanly, if possible. Enter the command s shutdown at the z/OS
console and reply to any messages produced. The message ALL FUNCTIONS COMPLETE
indicates that JES2 can now be stopped with the command $PJES2. After JES2 ends, System
z operation can be stopped. The 1090 is stopped with this command in the Linux window:
$ awsstop

4
If the 3270 session displays an “Unsupported Function” message, simply use the 3270 Clear key to obtain the
initial VTAM display. Some TN3270e emulators encounter this initial message and others do not.

Chapter 2. AD CD z/OS installation 23

 This produces a number of messages. It may be necessary to press Enter to obtain the Linux
prompt. Any 3270 windows may be closed at this point.

2.4.6 Startup messages

Messages such as:
AWSSTA014I Map file name specified: aprof9
0 Snapdump incident(s), RAS trace and RAS log files occupy 657046 bytes
in /home/ibmsys1/z1090/logs
Associated files, logs, and core files occupy 10364 bytes in
/home/ibmsys1/z1090/logs

are produced by the awsstart command. You should glance at these messages. Snapdump
incidents are indications of an internal 1090 error. If you want to work with IBM 1090 support
you will need this data. The number of bytes used for various logs and dumps is usually not
significant unless it becomes too large. To a great extent, the 1090 manages these files
automatically. However, if the numbers displayed become too large (many megabytes) and if
you are not actively working on a problem with IBM 1090 support, you may want to clean up
these files. This can be done by adding the --clean option the next time you issue an
awsstart command:
$ awsstart aprof11 --clean

You can get the --clean behavior every time by setting a Linux shell environment variable
Z1090_CLEAN=YES; however, we do not recommend doing this because it could easily
result in the removal of important debugging information in the event of a 1090 failure.

2.4.7 Local volumes

The process for adding your own 3390 volumes is as follows:
򐂰 Allocate the volume using the 1090 utility:
$ alcckd /z/WORK01 -d3390-1
򐂰 Update the devmap to include the new volume. (Assume address AA0 for this example.)
[manager]
name awsckd 0001
...
device AA0 3390 3990 /z/WORK01
򐂰 Restart zPDT with the updated devmap.
򐂰 IPL z/OS with the new volume present. z/OS will detect an uninitialized volume and vary it
offline.
򐂰 Create and run an ICKDSF job to initialize the volume:
//BILLX JOB 1,OGDEN,MSGCLASS=X
// EXEC PGM=ICKDSF,REGION=1M
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
INIT UNIT(AA0) NOVERIFY VOLID(WORK01) VTOC(0,1,14)
/*
򐂰 Vary the new volume online and begin using it:
VARY AA0,ONLINE (on the z/OS console)

24 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
2.5 z/OS parameters
We5 recommend that you make sure that the MIH6 values for both GRAF and COMM devices
are set to 3 minutes in the IECIOSxx member in your PARMLIB. Three minutes is the default
value, but we have seen some installations with a lower value specified. For example, you
could have a PARMLIB member named IECIOS00, as follows:
MIH GRAF=3:00
MIH COMM=3:00

To use the IECIOS00 member, your IEASYSxx PARMLIB member should contain the
following line:
IOS=00,

2.6 Multiple operating systems

We can install multiple System z operating systems, limited only by the disk space we have
available. Every emulated 3390-3 volume uses approximately 2.8 GB of disk space. Many of
our mobile computer disks were nominally 100 GB. After allowances for Linux and other
purposes we had about 82 GB of usable space left. This translates to 29 3390-3 volumes. (Of
course, there is no requirement to use 3390-3 volumes. A similar computation may be done
for other or mixed 3390 sizes.) We frequently placed emulated volumes on an inexpensive
USB drive and we did not see a significant performance difference between this drive and the
mobile computer internal hard disk. More recent mobile computer machines have even larger
hard disks.

It is important to distinguish between installing additional emulated 3390 volumes (perhaps

with a variety of operating systems), and using the volumes. We can, of course, only IPL a
single system at any one time in a 1090 instance.7 The volumes that may be “seen” by that
system depend on several factors:
򐂰 Does the current devmap contain all the desired volumes?
We can have multiple devmaps, each with a different selection of emulated volumes and
assigned addresses, but we can have only one devmap specified when we start a 1090
instance. We cannot change the devmap while the 1090 is running.8
򐂰 Do the device addresses in the devmap match suitable addresses in the IODF of the z/OS
system?
For example, if one of the emulated 3390 volumes is assigned address 120 (in the
devmap), then the default z/OS AD-CD IODF will consider it to be a 3380 volume instead
of a 3390 volume. (z/VM does not have predefined addresses for various device types,
making this aspect of z/VM easier to use.)
򐂰 Duplicate disk volsers may not be present.
You may have duplicate volsers for emulated volumes on your PC disk, but the duplicates
should not be present in a given devmap.
򐂰 It may not be possible to use the common addresses typically associated with an
operating system.

5
The 1090 developers have recommended this parameter set. However, we very seldom see the need for it and
suggest that you might skip it unless you encounter 3270 connection timeouts.
6 This is the Missing Interrupt Handler function.
7
This statement ignores the possibility of running multiple z/OS guests under z/VM.
8
This is not completely true. We can change the volume mounted on an emulated disk drive or tape drive with the
awsmount command.

Chapter 2. AD CD z/OS installation 25

 For example, all the AD-CD documentation uses A80 as the IPL address for a z/OS
AD-CD system. We can have two (or more) AD-CD systems installed at the same time,
but only one volume can have address A80 during any single execution of the 1090. This
does not prevent us from IPLing any of the (multiple) AD-CD systems installed, but we
need to specify the correct address. An example might make this clearer:
Address VOLSER Purpose
A80 ZCRES1 IPL volume for z/OS 1.12 AD system
A81 ZCRES2 Libraries for z/OS 1.12 AD system
A82 ZCSYS1 Paging, spooling, VSAM for 1.12 AD system
...
A90 SBRES1 IPL volume for z/OS 1.11S system
A91 SBRES2 Libraries for z/OS 1.11S system
A92 SBSYS1 Paging, spooling, VSAM for 1.11S system
...
Assuming our devmap is configured for these addresses, we can ipl A80 parm 0A82CS
to run the 1.12 system or we can ipl A90 parm 0A92CS to run the 1.11S system. In
either case, the running z/OS system can access all the volumes of both z/OS
systems. This is very convenient for migration purposes. The volumes are readdressed
by simply changing the addresses in the devmap.

We can run multiple System z operating systems at the same time by starting multiple zPDT
instances, but this requires more resources (especially PC memory). Details about using
multiple instances are in Volume 3 of this documentation series.

26 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 3

Chapter 3. LANs and TCP/IP

LAN setup can be complex and many variations are possible. We have selected five basic
scenarios as possible starting points. We strongly suggest that your initial zPDT usage be
with scenario 1, which has no System z TCP/IP functions.1 The second scenario is then a
simple migration from the first one. The third, fourth, and fifth scenarios provide different ways
to connect zPDT functions to an external network. The key difference between these last
three scenarios is whether you have an assigned, fixed IP address that can be used with your
z/OS (or z/VM, or z/VSE, or Linux for System z).

This chapter does not address more complex LAN usage, such as might be used for multiple
guests under z/VM. Some elements of z/VM usage are addressed by examples in the third
book in this series, but there are many combinations and permutations that we cannot
address. Again, we strongly suggest you start with the basic scenarios described in this
chapter. After working through these you should then be familiar with the elements of LAN
usage that are unique to zPDT.

We also strongly suggest that you take time to study this chapter before starting your LAN
setup. We assume you have some familiarity with z/OS system programming tasks. The
following discussions are in terms of z/OS, but most of the concepts also apply to z/VM and
z/VSE.

Important: LAN setup is not part of the zPDT product. The examples in this chapter may
help you decide how to configure your TCP/IP set up, but you must provide the networking
skills to verify and implement your own design.

1 If you follow the installation instructions in the first two chapters, you will be close to this environment.

© Copyright IBM Corp. 2009, 2011. All rights reserved. 27

3.1 Overview of LAN usage
There are three key factors that permeate this discussion and you should keep them in mind:
򐂰 You do not need any z/OS LAN functions (or z/OS TCP/IP functions) for 3270 access to
z/OS. Access can be via the aws3274 device manager and appears as local,
channel-attached terminals to z/OS. This is our first scenario.
򐂰 z/OS and the base Linux cannot communicate with each other through the same LAN
adapter. Both can share the same LAN adapter for all TCP/IP functions except
communicating with each other. zPDT implements a tunnel2 pseudo-LAN to bypass this
restriction.
򐂰 z/OS is not a DHCP client. You cannot simply plug z/OS into any LAN outlet on your office
wall. To connect to z/OS TCP/IP you must have a fixed IP address that is valid on your
physical LAN segment.

At the time of writing, Linux bonding of several LAN adapters to create a single virtual adapter
is not usable with zPDT.

3.1.1 Three 3270 interfaces

There may be three 3270 interfaces with z/OS:
򐂰 The aws3274 device manager accepts TN3270e connections3 (from the local Linux host
or over the Linux TCP/IP network.) The Linux TCP/IP port number for this connection is
specified in the 3270port parameter in the devmap. z/OS sees these 3270 sessions as
local, channel-attached, non-SNA, DFT terminals. Such terminals are suitable for z/OS
operator consoles and VTAM use. z/OS TCP/IP is not involved and need not be running.
򐂰 z/OS TCP/IP provides TN3270e connections. Terminals connected this way are not
usable as z/OS operator consoles. TN3270e connections through z/OS TCP/IP are routed
to VTAM and may be used as TSO terminals, CICS® terminals, and so forth. z/OS TCP/IP
must be configured to use an OSA-Express2 adapter (in either non-QDIO or QDIO mode).
The OSA-Express2 functions are emulated by the awsosa device manager.4
򐂰 z/OS VTAM potentially could work with SNA 3270 Ethernet connections, working through
the awsosa device manager. However, SNA operation with the 1090 is not supported at
this time.

The same Ethernet adapter can be used for Linux functions, such as telnet, aws3274, ftp, and
so forth, and also for OSA connections. Important concepts include the following:
򐂰 An emulated OSA-Express interface requires a hardware Ethernet adapter port on the
underlying Linux system (or a tunnel interface, as described later). A mobile computer
normally has one integrated Ethernet port. (It may also have integrated wireless
functions.) Additional Ethernet ports may be added by using PC (PCMCIA-type) cards,
although very few zPDT users are expected to need more than one Ethernet adapter.
򐂰 An emulated OSA-Express interface operating in QDIO mode is used only for z/OS
TCP/IP (or z/VM TCP/IP, and so forth).

2 In strict Linux terminology we do not have a tunnel interface; we use a tap interface rather than a tun interface. We
use the word tunnel in a more generic sense.
3
A TN3270 connection (as opposed to a TN3270e connection) will be accepted, but extended data stream
capabilities are not present and some z/OS functions may not work correctly.
4
We describe this as an OSA-Express2 device manager, but this description is only approximate. This device
manager has attributes of both the original OSA, OSA-Express, and OSA-Express2 channels available on larger
System z machines.

28 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 򐂰 An emulated OSA-Express interface operating in non-QDIO mode can be used by z/OS
TCP/IP or SNA (although SNA is not supported at this time). Non-QDIO mode is
sometimes known as LCS mode.
򐂰 If you want to communicate between Linux TCP/IP and OSA TCP/IP on the same PC, a
tunnel environment must be established.5

3.2 Basic QDIO setup

The examples below assume that OSA is used as a QDIO device, as opposed to an LCS
(non-QDIO) device. An overview of LCS usage is provided in the third volume in this
documentation series. We recommend using QDIO operation. For QDIO operation:
򐂰 Three OSA devices are needed for a TCP/IP connection. The first should be at an
even-number address.
򐂰 z/OS devices involved must be defined as OSA devices in the z/OS IODF.
򐂰 A TRLE definition is needed in VTAMLST, pointed to by ATCCON00 in VTAMLST.
򐂰 The z/OS TCPIP PROFILE uses a IPAQENET device type.

The awsosa definitions must include path numbers and path types for OSA devices. The path
type is OSD (for QDIO). The path is determined with the find_io command on your system.
We cannot predict exactly what that path might be.

Recent z/OS AD-CD systems include OSA devices starting at device number 400. When
using the QDIO interface to the emulated OSA-Express2 function, the key parameters might
look like the following:6
Devmap

[manager]
name awsosa 22 --path=F0 --pathtype=OSD
device 400 osa osa
device 401 osa osa
device 402 osa osa

Or the following for a tunnel connection

[manager]
name awsosa 22 --path=A0 --pathtype=OSD --tunnel_intf=y
device 400 osa osa
device 401 osa osa
device 402 osa osa

z/OS VTAMLST

OSATRL1 VBUILD TYPE=TRL

OSATRL1E TRLE LNCTL=MPC,READ=(400),WRITE=(401),DATAPATH=(402), X
PORTNAME=PORTA,MPCLEVEL=QDIO

5
Another method would use two Ethernet adapters connected to the same network, one for the base Linux and one
for z/OS. We do not recommend this method.
6 This example might be appropriate for an OSA LAN connection via an Ethernet adapter.

Chapter 3. LANs and TCP/IP 29

 z/OS TCP/IP Profile

DEVICE PORTA MPCIPA

LINK ETH1 IPAQENET PORTA
HOME 192.168.0.61 ETH1
...
BEGINRoutes
; Destination Subnet Mask FirstHop Link Size
ROUTE 192.168.0.0 255.255.255.0 = ETH1 MTU 1492
ROUTE DEFAULT 192.168.0.1 ETH1 MTU 1492
ENDRoutes
...
START PORTA

The presence of the --tunnel_intf parameter in the devmap indicates that a tunnel (tap device)
connection will be created. The default address for the Linux side of a tunnel is 10.1.1.1. The
--path value is the CHPID number returned by the find_io command. The CHPID value is
usually A0 for a tunnel connection, F0 for a direct Ethernet LAN connection, or F8 for a
wireless connection.

A VTAM major node known as a TRL is required in VTAMLST for QDIO operation. This VTAM
node must be active before TCP/IP can be started. The VTAMLST ATCCON00 member must
point to the TRL entry in VTAMLST.

The MIH value set for the write interface (401 in the example) should be set to at least 30
seconds.7 (The default value is usually sufficient.)

The PORTNAME (in the TRLE), the DEVICE name (second field), the LINK parameter (fourth
field), and the START name must match. The name is arbitrary, but it must be the same in all
four places.

3.3 Five scenarios

Five scenarios are described in this chapter. We use z/OS as the target operating system in
these descriptions, but z/VSE or z/VM or Linux for System z could be used with appropriate
adjustments. We use QDIO (OSD) interfaces for these examples, although LCS (OSE)
interfaces could be used.8 QDIO usage in z/OS requires parameters in VTAMLST, and these
are included in the setup examples.

The five scenarios are:

1. No TCP/IP function is used in z/OS. Only emulated local 3270 connections are used
between the base Linux and z/OS. The base Linux could be connected to a larger LAN;
this is transparent to z/OS. Emulated 3270 sessions from the base Linux or from the LAN
can connect to z/OS, where they appear as local, channel-attached 3270 sessions.
2. z/OS TCP/IP is used to connect to the base Linux via a tunnel function.9 All z/OS TCP/IP
activity is directed to the tunnel. This allows TCP/IP connections between the base Linux
and z/OS, and these might be used for ftp, telnet (to UNIX System Services), TN3270
connections directly to z/OS TCP/IP, and so forth. The base Linux could be connected to
7
This was recommended by the developers. In routine usage we have not seen any problems using the default z/OS
MIH values.
8 We recommend using QDIO interfaces for several reasons. QDIO connections are faster and are not as exposed to
packet saturation as LCS interfaces.
9
The correct terminology is “connect via a Linux tap interface.” However, we use the term “tunnel” in a generic sense
to describe this connection.

30 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 an external LAN, but this is transparent to z/OS and external LAN connections cannot be
made to z/OS.
3. The same basic setup as scenario 2, but with additional customization to enable a simple
NAT function in the base Linux. This permits TCP/IP connections from z/OS to the
external LAN, but not from the external LAN to z/OS. (That is, only outgoing TCP/IP
sessions may be initiated. With additional NAT/iptables customization, incoming TCP/IP
connections from the external LAN to z/OS could be handled. This additional
customization may involve non-standard port numbers for either Linux or z/OS.)
4. Instead of the NAT functions used in option 3, an additional OSA interface is used by z/OS
to connect to the LAN. A fixed IP address is needed for z/OS. TCP/IP communication
between z/OS and the base Linux is via the tunnel.
5. A different NAT function is used that allows incoming and outgoing connections to z/OS. In
this scenario, only the tunnel OSA is used by z/OS and both tunnel and external LAN
traffic flow through it. The z/OS setup is the same as for scenario three, but the base Linux
setup is different. A fixed IP address is needed for z/OS.

In these examples, the names assigned to the OSA interfaces for z/OS are eth1 and eth2 (if
needed). These examples use eth1 for the tunnel connection to the base Linux. These names
are completely arbitrary.

OSA definitions for zPDT require the use of a CHPID number for the path parameter. The
CHPID path for the tunnel is assumed to be A0 and the path for the external LAN is assumed
to be F0. These paths should be verified with the zPDT find_io command. This command
might not display information for tap devices until after zPDT has been started at least once
with a tunnel definition included in the devmap.

Figure 3-1 suggests a way to select the most appropriate scenario.

This choice means a LAN no

connection only between Need LAN to z/OS? Scenario 1 end
the base Linux and z/OS
yes

Need external LAN no end

Scenario 2
connection to z/OS?
yes

Scenario 4 yes Have assigned, fixed no Scenario 3

or IP address for z/OS?
Scenario 5

Want name server

yes available to z/OS? no end

Customize GLOBAL Issue MVS command for

data RESOLVER REFRESH

no Make RESOLVER yes Customize SYS1.PROCLIB

end and BPXPRMxx members
changes permanent?

Scenarios 3 and 5 require running a Linux script file before starting zPDT

Figure 3-1 Scenario overview

Scenarios 3 and 5 produce similar results in different ways. Scenario 3 requires more
customization in z/OS TCP/IP and scenario 5 requires more customization in the base Linux.

Chapter 3. LANs and TCP/IP 31

3.3.1 Scenario 1
Scenario 1 is illustrated in Figure 3-2.

local channel-connected 3270s

Linux base z/OS

PCOM, IOS
x3270 aws3274
VTAM

x3270
(No TCP/IP)
network
TCP/IP
LAN adapter

DHCP or fixed IP address

The Linux connection to the outside world is
optional. If connected, it may be via DHCP or
Scenario 1 a fixed IP address.

Figure 3-2 Scenario 1 connectivity

With this option, no z/OS TCP/IP setup is required and z/OS TCP/IP need not be active. (The
AD-CD z/OS system starts TCPIP by default; you could remove the associated start
statement.) You can use up to 31 TN3270 sessions for connections to TSO or other VTAM
functions. (One TN3270 session is needed for the MVS™ console.) A variety of TN3270
emulators can be used, including x3270 and PCOMM. These 3270 emulator sessions might
be in the base Linux or via a LAN connection to the base Linux, if this exists. (The LAN
connection to an external network is optional.) The only upload/download method between
the base Linux and z/OS is by using the IND$FILE functions.10

No OSA definitions are needed in the devmap. The relevant devmap definitions are for the
3270 port and for several local 3270 devices.
[system]
....
3270port 3270 #the port number is arbitrary. 3270 is easy to remember.

[manager]
name aws3274 0001
device 0700 3279 3274 #Address 0700 is the MVS console in the AD-CD systems
device 0701 3279 3274 #Other systems may want different addresses
device 0702 3270 3274
...

Based on this example, connections from the base Linux might start as follows:
$ x3270 -port 3270 localhost &

A connection from the external LAN might be started as follows:

$ x3270 -port 3270 9.111.222.123 &

assuming the DHCP address assigned to the local Linux is 9.111.222.123. You can find the
assigned DHCP address for your Linux with the /sbin/ifconfig command.

10 These are often known as file transfer functions in the 3270 emulators.

32 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 Making a TN3270 connection to aws3274 on the base Linux (or any other service on the base
Linux) from an external LAN, may present routing difficulties. The LAN must have route
definitions that allow both the external TN3270 system and the base Linux to find routes to
each other. This routing requirement is not unique to zPDT, of course. If you have a firewall
running in the base Linux, you may need to create a “hole” in it for the connection to port 3270
(or whatever port you defined for aws3274 connections). If your firewall is based on iptables
(as is common for most current Linux releases), commands such as:
$ su (switch to root)
# iptables -I INPUT -p tcp --dport 3270 -j ACCEPT
# exit (leave root)

might be used. These commands would be entered through a Linux terminal window. In
general, managing your Linux firewall and your external routing controls is beyond the scope
of this document.

3.3.2 Scenario 2
The second scenario builds on the first one and adds a direct TCP/IP connection between
z/OS and the base Linux, as shown in Figure 3-3.

local channel-connected 3270s

Linux base z/OS

PCOM IOS
x3270 aws3274
one OSA
port for z/OS VTAM

x3270
eth1 TCP/IP
network tap0 10.1.1.2
TCP/IP 10.1.1.1

LAN adapter
DHCP or fixed IP
Scenario 2
Figure 3-3 Scenario 2 connectivity

This TCP/IP connection is through a “tunnel” interface between z/OS and the base Linux. The
physical LAN adapter is not involved.11 The IP addresses shown are arbitrary, but we
recommend using non-routable addresses on an isolated subnet. The tap interface (and
associated IP address) are created automatically when zPDT is first started (assuming the
correct OSA definitions are in the devmap). No additional Linux setup is needed. z/OS
TCP/IP must include an OSA definition for its interface.

Recent AD systems include OSA devices starting at device number 400. When using the
QDIO interface to the emulated OSA-Express2 function, the key parameters might look like
the following:
Devmap

(The 3270 port and aws3274 device manager definitions used in the
previous example should be included here.)

[manager]
11 This connection cannot use a physical LAN adapter on current Linux systems.

Chapter 3. LANs and TCP/IP 33

 name awsosa 22 --path=A0 --pathtype=OSD --tunnel_intf=y
device 400 osa osa
device 401 osa osa
device 402 osa osa

z/OS VTAMLST

OSATRL1 VBUILD TYPE=TRL

OSATRL2E TRLE LNCTL=MPC,READ=(400),WRITE=(401),DATAPATH=(402), X
PORTNAME=PORTA,MPCLEVEL=QDIO

z/OS TCP/IP Profile

...
DEVICE PORTA MPCIPA
LINK ETH1 IPAQENET PORTA
HOME 10.1.1.2 ETH1
...
BEGINRoutes
; Destination Subnet Mask FirstHop Link Size
ROUTE 10.0.0.0 255.0.0.0 = ETH2 MTU 1492
ROUTE DEFAULT 10.1.1.1 ETH2 MTU 1492
ENDRoutes
...
START PORTA

The external LAN connected to Linux and the “tunnel LAN” between Linux and z/OS are
completely separate in this example, and there is no communication between them. There is
no connection from z/OS to the outside world, but all normal TCP/IP functions between the
base Linux and z/OS may be used. Examples (from the Linux side) include:
$ x3270 -port 3270 localhost & (connect via “local 3270” channel)
$ x3270 10.1.1.2 & (connect to z/OS TCP/IP)
$ ftp 10.1.1.2 (connect to z/OS FTP)
$ telnet 10.1.1.2 102312 (connect to z/OS UNIX System Services)

From the z/OS TSO side, we might use a command such as:
ftp 10.1.1.1 (entered in ISPF option 6, for example)

to connect to ftp on the base Linux. (This assumes you have ftp installed and available on the
base Linux.)

Tunnel IP addresses
The IP addresses used for the tunnel (10.1.1.1 and 10.1.1.2 in the examples) are not related
to any other IP addresses you might use. They are not related to any external IP addresses.
They should not be on the same subnet as any external IP addresses you might use. These
tunnel addresses are solely for use between the base Linux and TCP/IP stacks running within
the zPDT environment.

The IP address for the base Linux side of the tunnel defaults to 10.1.1.1 (for the first tunnel
OSA). The address at the other end (z/OS or z/VM) must be different but should be on the
same subnet as determined by the netmask.

12 The AD-CD z/OS system uses port 1023 for a simple telnet connection to UNIX System Services.

34 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 The 10.x.x.x addresses (and 192.168.x.x addresses) are not routable. You should not attempt
to make them visible to your network users. (In our examples, the 192.168.x.x addresses are
assumed to be on the “local side” of a router (which is probably a NAT router). As used in our
examples, the 192.168.x.x addresses are visible and usable by other systems connected to
the local side of this router.

3.3.3 Scenario 3
Scenario 3 is depicted in Figure 3-4.

local channel-connected 3270s

Linux base z/OS

PCOM IOS
x3270 aws3274
VTAM
one OSA
port for z/OS
x3270
eth1 TCP/IP
network tap0
TCP/IP 10.1.1.1 10.1.1.2

DHCP or fixed IP
iptables used default route to
to create NAT 10.1.1.1
Scenario 3 environment
Figure 3-4 Scenario 3 connectivity

We can take the scenario 2 setup and extend it to connect z/OS to the external LAN by using
a NAT13 function in the base Linux. This requires a more complex setup. However, it has the
major advantage that an assigned, fixed IP address is not needed for z/OS. With this setup,
z/OS has the fixed address 10.1.1.2 (in our examples), but this is not an externally assigned
address; it is visible only internally in our local Linux system.

The following text describes how to do this dynamically (via commands each time the system
is started). This example is based on openSUSE 11.0; there may be minor differences for
other Linux distributions.

The first step is to create a Linux file in the zPDT home directory. We named this file masq.
$ cd ~
$ touch masq
$ gedit masq (the following lines start in column 1 in the file)
if [[ $EUID -ne 0 ]]; then
echo ‘You must su to root to run this command’ 1>&2
exit 1
fi
echo ‘Your firewall must be enabled for this command to be meaningful’
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -F FORWARD
iptables -P FORWARD ACCEPT
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
iptables -I INPUT -p tcp --dport 3270 -j ACCEPT

13 NAT is Network Address Translation.

Chapter 3. LANs and TCP/IP 35

 echo ‘Done. Exit from root’

Use the same devmap and z/OS PROFILE parameters shown for scenario 2. Assuming your
base Linux is connected to an external LAN (either with a fixed IP address or a DHCP
address), activate your Linux firewall (if not already done) and activate the iptable changes:
$ cd ~
$ su (switch to root)
# ./masq (execute the command script we just created)
# exit (exit from root)

You should be able to access external network sites from z/OS. For example, at the time of
writing the www.redbooks.ibm.com site is IP address 170.225.15.45. From a TSO command
line you can try the following command:
ftp 170.225.15.45

You need an appropriate userid and password to use this site, but you should see the ftp
connection. You should be able to ping any Internet sites that are known to respond to
pings,14 provided you can find their numeric IP address.

You may need to use the passive option with ftp connections. Complex applications that, once
initiated from z/OS, might trigger incoming connections on other ports may not work.
Incoming connections to port 3270 on the base Linux are allowed by our script; this provides
a hole in the standard Linux firewall for using the local 3270 connections.

Incoming connections
This setup has complications for incoming (from the external LAN) connections. Remember
that external systems see only the IP address of the base Linux. (This is probably a
DHCP-assigned address, and must be communicated to external users in some manner.) If
an external user attempts to connect to port 23, for example, should he connect to Linux port
23 or z/OS port 23? (This assumes he can get through the Linux firewall, which is another
complication.) Port 23 is a well-known (default) port number for telnet connections (including
TN3270e telnet).15

One way around this problem is to use a non-standard port number for telnet on either Linux
or z/OS. Another way around the problem is to simply disallow port 23 connections to either
Linux or z/OS. (The issue applies to all port numbers; we are using port 23 as an example.)

As an example, adding the following line to the script would route external connections for
port 23 to z/OS:
iptables -t nat -A PREROUTING -p tcp -i eth0 --dport 23 -j DNAT --to 10.1.1.2

If we add this command to our script, then an external user would have two paths for a
TN3270e connection (assuming the Linux IP address is 192.168.0.2):
$ x3270 192.168.0.2 & Connect directly to z/OS TCP/IP port 23
$ x3270 192.168.0.2:3270 & Connect to Linux port 3270 (aws3274)

Of course, once this iptables command is issued, we no longer have a way to connect to
Linux port 23.

14 It appears that most common Internet sites no longer respond to pings. You can verify your results by issuing
pings from the base Linux system.
15
Some Linux systems have completely dropped telnet service (that listens on port 23); our comments apply to all
ports.

36 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 Extending this example to other ports, and determining what services might be wanted on
both Linux and z/OS becomes more complex and depends on the exact base Linux
configuration for firewalls and available services.

3.3.4 Scenario 4
This setup provides a direct connection from z/OS to the external LAN. A NAT function is not
used. Only a single physical LAN adapter is needed and is used by both Linux and z/OS.
z/OS must have an external assigned, fixed IP address for this to work. Our example uses
address 192.168.0.61, but this is not a real assigned IP address16; you must have a proper
assigned IP address for this option to work. Please remember that assigned, fixed IP
addresses are not very portable; they must be used on a physical LAN segment that is the
router target for the associated subnet.

Figure 3-5 illustrates this configuration. The figure shows two logical connections to the
external network, but this is accomplished by a single physical cable connection.

local channel-connected 3270s

Linux base z/OS

PCOM IOS
x3270 aws3274
VTAM

10.1.1.2 TCP/IP
x3270 eth1
tap0
10.1.1.1
network
TCP/IP
eth2
192.168.0.61

two OSA
DHCP or fixed IP for Linux fixed IP address for z/OS ports for z/OS
(still one physical LAN adapter)
Scenario 4 the “fixed” address

Figure 3-5 Scenario 4 connectivity

With this configuration the IP functions of z/OS and the base Linux are quite separate. The
tunnel addresses (10.1.1.x) are not visible from the external network.

The various definition files should contain the following:

Devmap

(The 3270 port and aws3274 device manager definitions used in the
previous examples should be included here.)

[manager]
name awsosa 0024 --path=A0 --pathtype=OSD --tunnel_intf=y
device 400 osa osa
device 401 osa osa
device 402 osa osa

[manager]
16
IP addresses 192.168.0.0 are “nonroutable” addresses that can be used on a local network that is not connected
to external networks.

Chapter 3. LANs and TCP/IP 37

 name awsosa 0022 --path=F0 --pathtype=OSD
device 404 osa osa
device 405 osa osa
device 406 osa osa

z/OS VTAMLST

OSATRL1 VBUILD TYPE=TRL

OSATRL1E TRLE LNCTL=MPC,READ=(400),WRITE=(401),DATAPATH=(402), X
PORTNAME=PORTA,MPCLEVEL=QDIO
OSATRL2E TRLE LNCTL=MPC,READ=(404),WRITE=(405),DATAPATH=(406), X
PORTNAME=PORTB,MPCLEVEL=QDIO

z/OS TCP/IP Profile

DEVICE PORTA MPCIPA

LINK ETH1 IPAQENET PORTA
HOME 10.1.1.2 ETH1

DEVICE PORTB MPCIPA

LINK ETH2 IPAQENET PORTB
HOME 192.168.0.61 ETH2

...
BEGINRoutes
; Destination Subnet Mask FirstHop Link Size
ROUTE 10.0.0.0 255.0.0.0 = ETH1 MTU 1492
ROUTE 192.168.0.0 255.255.255.0 = ETH2 MTU 1492
ROUTE DEFAULT 192.168.0.1 ETH2 MTU DEFAULTSIZE
ENDRoutes
...
START PORTA
START PORTB

Again, remember that the 192.168.x.x addresses cannot be used for “real” Internet
connections. You must supply your assigned, fixed IP address and also supply a default
address for your network connection.

With this scenario, connections to/from z/OS and the external network are independent from
base Linux connections. However, you must still use the 10.1.1.x addresses for TCP/IP
communication between the base Linux and z/OS. That is why we show two OSA definitions
and connections in this example.

38 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
3.3.5 Scenario 5

local channel-connected 3270s

Linux base z/OS

PCOM IOS
x3270 aws3274
VTAM
one OSA
port for z/OS
x3270
eth1 TCP/IP
network tap0
TCP/IP 10.1.1.1 10.1.1.2

DHCP and fixed IP

iptables used default route to
to create NAT 10.1.1.1
Scenario 5 environment
Figure 3-6 Scenario 5 connectivity

We can take the scenario 2 setup and extend it to connect z/OS to the external LAN by using
a NAT function in the base Linux in a different way. This method requires an assigned, fixed IP
address for z/OS. A single OSA interface in z/OS handles both tunnel traffic (to the base
Linux) and external IP traffic. Incoming connections to z/OS are handled, as well as outgoing
connections.

The following text describes how to do this dynamically (via commands each time the system
is started). Note that this method uses an IP alias address in the base Linux. This was not
supported by zPDT until release 39.16 (February 2010).

The first step is to create a Linux file in the zPDT home directory. We use a more elaborate
script file here to better allow it to be expanded in the future. We named this file nat2.
$ cd ~
$ touch nat2
$ gedit nat2 (the following lines start in column 1 in the file17)
if [[ $EUID -ne 0 ]]; then
echo ‘You must be root to run this command’ 1>&2
exit 1
fi
echo ‘Your firewall must be enabled for this command to be meaningful’
CHPID_A0_INTERFACE=eth0
CHPID_A0_EXTERNAL_IP=192.168.0.70 (your assigned IP address)
CHPID_A0_EXTERNAL_BC=192.168.0.255 (brodcast address for it)
CHPID_A0_EXTERNAL_NM=255.255.255.0 (net mask for it)
CHPID_A0_VIRTUAL_IP=10.1.1.2

echo 1 > /proc/sys/net/ipv4/ip_forward

echo ‘IP forwarding set’
iptables -t nat -F
echo ‘nat table flushed’

17
Four lines in this file end with a “back slash” to indicate that the logical line is continued on the next printed line.
You could enter each of these lines as a single long line (without the back slash).

Chapter 3. LANs and TCP/IP 39

 echo ‘External IP address for System z is ‘ $CHPID_A0_EXTERNAL_IP
echo ‘Real LAN interface is ‘ $CHPID_A0_INTERFACE
echo ‘Tap (tunnel) address for System z is ‘ $CHPID_A0_VIRTUAL_IP
echo ‘External netmask and broadcast address are ‘ $CHPID_A0_EXTERNAL_NM \
$CHPID_A0_EXTERNAL_BC

ifconfig $CHPID_A0_INTERFACE:0 $CHPID_A0_EXTERNAL_IP netmask \

$CHPID_A0_EXTERNAL_NM broadcast $CHPID_A0_EXTERNAL_BC up

iptables -t nat -A POSTROUTING -o $CHPID_A0_INTERFACE -s \

$CHPID_A0_VIRTUAL_IP/32 -j SNAT --to $CHPID_A0_EXTERNAL_IP

iptables -t nat -A PREROUTING -i $CHPID_A0_INTERFACE -d \

$CHPID_A0_EXTERNAL_IP/32 -j DNAT --to $CHPID_A0_VIRTUAL_IP

echo ‘Done. Please exit from root’

Use the same devmap and z/OS PROFILE parameters shown for scenario 2. Assuming your
base Linux is connected to an external LAN (either with a fixed IP address or a DHCP
address), activate your Linux firewall (if not already done) and activate the iptable changes:
$ cd ~
$ su (switch to root)
# ./nat2 (execute the command script we just created)
# exit (leave root)

You should be able to access external sites from z/OS. External LAN users can connect to
your base Linux by using its DHCP address18 and connect to z/OS by using its assigned fixed
address.

If you use LCS mode connections (non-QDIO, OSE) for some reason, this scenario has an
additional advantage. Unwanted packets are filtered out at the base Linux level instead of
being forwarded to z/OS, where many cycles may be required to filter out unwanted packets.

3.3.6 z/OS resolver

The z/OS resolver can access an external name server using the connections in scenarios 3,
4, and 5. There are a number of ways to do this, and the following is one example. It involves
creating or changing several data sets (or members) in z/OS. Our example uses data set
names from the AD-CD z/OS 1.12 winter release; you may need to adjust these names for
your z/OS system.
[create member ADCD.Z112.TCPPARMS(RSSETUP)]
GLOBALTCPIPDATA('ADCD.Z112.TCPPARMS(GLOBAL)')
GLOBALIPNODES('ADCD.Z112.TCPPARMS(IPNODES)')'
COMMONSEARCH

[create member ADCD.Z112.TCPPARMS(GLOBAL)]

TCPIPJOBNAME TCPIP
HOSTNAME yourname
DOMAINORIGIN ADCD.ITSO.IBM.COM (use an appropriate name here)
DATASETPREFIX TCPIP
MESSAGECASE MIXED
NSINTERADDR 167.206.251.130 (specify an appropriate name server)
NSPORTADDR 53
18 Of course, you could also have an assigned, fixed address for your base Linux.

40 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 RESOLVEVIA UDP
RESOLVERTIMEOUT 10
RESOLVERUDPRETRIES 1
LOOKUP DNS

[create member ADCD.Z112.TCPPARMS(IPNODES)] (may not be needed)

167.206.251.130 nameserver

You need a nameserver that is available to you. You might find one by issuing a Linux
command such as nslookup www.ibm.com and noting what server was used to resolve the
name.

The AD-CD system (at the time of writing) starts the resolver using the default name
RESOLVER. Assuming this situation, issue the following commands at the MVS console:
F RESOLVER,DISPLAY (verify that the resolver is running)
F RESOLVER,REFRESH,SETUP=ADCD.Z112.TCPPARMS(RSSETUP)

where the specified setup file is the one created earlier. When this is working correctly, you
should be able to use the following commands from TSO:
NSLOOKUP WWW.REDBOOKS.IBM.COM
PING WWW.REDBOOKS.IBM.COM
FTP WWW.REDBOOKS.IBM.COM

The www.redbooks.ibm.com site is just an example, of course.

The use of an Internet name server can be more complex than indicated here. If you fully
connect to a name server you should take care to specify an appropriate domain and host
name for your own system that does not duplicate any existing name that might be resolved
by an Internet name server.

Permanent changes
The resolver changes can be made permanent (automatically used by z/OS TCP/IP) by
changing the BPXPRMxx members in your PARMLIB. To do this, first create the following
procedure in SYS1.PROCLIB(RESOLVAD):19
//RESOLVAD PROC PARMS='CTRACE(CTIRES00)'
//EXBREINI EXEC PGM=EZBREINI,REGION=0M,TIME=1440,PARM=&PARMS
//SETUP DD DSN=ADCD.Z112.TCPPARMS(RSSETUP),DISP=SHR,FREE=CLOSE

Next, identify the BPXPRMxx member(s) in ADCD.Z112.PARMLIB that are used by your IPL
parameters. This is likely to include BPXPRMCS for recent AD-CD releases. You can change
all the BPXPRMxx members that you might use. Edit these members and add the following
line as the last line in each member (after a blank line):
RESOLVER_PROC(RESOLVAD)

The ADCD.Z112.PARMLIB name should be adjusted to match your AD-CD release, of

course. The member names RESOLVAD, RSSETUP, GLOBAL, and IPNAMES are arbitrary
names. You will probably want to add the following command to your SHUTDOWN scripts20
to terminate the resolver:
P RESOLVAD

19
Member name RESOLVAD is arbitrary. The procedure should be in SYS1.PROCLIB because it is started under
MSTR, the master scheduler.
20 These scripts are in the AD-CD PARMLIB data set, with names such as SHUTDOWN, SHUTALL, and so forth.

Chapter 3. LANs and TCP/IP 41

 Ways to make the iptables commands automatic (in the base Linux) vary with different Linux
levels and distributions, and we leave this as an exercise for you. (The author simply executes
the small iptables script manually before starting zPDT.)

See the following document for more resolver setup information: Communications Server for
z/OS V1R9 TCP/IP Implementation Volume1: Base Functions, Connectivity, and Routing,
SG24-7532.

3.3.7 Debugging LAN setups

Creating a working LAN environment can be frustrating because many details must work
together. Sometimes the problem lies outside your environment, with external routers that are
not adapted for the “new” systems you are placing on the LAN. We suggest using a small,
inexpensive personal router for initial zPDT LAN setup, as shown in Figure 3-7.

optional wireless
connection to Linux
and your other local
connect to PCs
external
LAN “local connections”
(optional) Linux and
zPDT

small
personal another
router Linux
(probably
with x3270

Windows
192.168.1.x (and PCOMM)

Figure 3-7 LAN debugging setup

The advantage of using this test setup is that there are no unknown external LAN
complications. The “local connections” to the router can be served DHCP addresses by the
router, or they can be assigned fixed addresses on the router subnet. These routers typically
use IP addresses of 192.168.0.x or 192.168.1.x. Many such routers also provide wireless
connections and you can also explore these. (We suggest initial use with a wired connection
to Linux, just to simplify the first setup.)

Once you have an environment like this working you can then transfer operation to a larger
network. While this suggested environment is almost trivial, we have found it very useful
many times.

Remember that the Linux firewall (if enabled) may affect any external connections. For initial
debugging (especially in a private environment, as shown here) we suggest that the firewall
be disabled until you verify that your basic LAN setup is working. We have observed that the
SEL21 protection may need to be disabled or modified for some functions, such as ftp.

21 Security Enhanced Linux

42 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
3.3.8 Performance problems
At the time of writing we were aware of two particular problems that impact OSA performance.
򐂰 If frames larger than expected are used, there may be an excessive number of frames
dropped (causing a retransmission). This might not be noticed unless careful
measurements or comparisons are made. We believe this problem is resolved by including
the systcl parameter:
net.core.rmem_max=4194304
that is now recommended in the first chapter of this document.
򐂰 If advanced Linux kernels are installed there might be a drastic slow-down of OSA
performance that would be immediately obvious. This is due to Linux attempting to offload
checksum functions into the adapter, which is not acceptable to the current awsOSA
implementation. One solution is to use a Linux command:
# ethtool -K eth0 rx off
Unfortunately, this command must be entered after each Linux boot. The problem was first
noticed with a build of Linux kernel 2.6.36.2; the ethtool must be at least at level 2.6.33.
We have not seen this problem with any of the “standard” Linux distributions that we have
referenced in these documents.

IBM has not published any performance specifications for OSA. Informal observation
indicates that ftp throughput may be in the 5-8 megabytes/second range, assuming an
unconstrained network in a dedicated environment. If your performance is much worse than
this, the two problems mentioned here might be reviewed.

3.3.9 Detailed scenario comparison

Table 3-1 provides a summary of the characteristics of these five scenarios. Pay attention to
the from and to words in the descriptions.

Table 3-1 Scenario characteristics

Characteristic 1 2 3 4 5

Number of local 3270 sessions from 32 32 32 32 32

base Linux (including external LAN) to
z/OS (using one aws3274 manager)

Number of OSA definitions in z/OS 0 1 1 2 1

Number of “command files” needed to 0 0 1 0 1

run in base Linux

External LAN connection from/to z/OS no no yesb yes yes

(not counting local 3270 sessions)a?

TN3270, ftp, telnet from local Linux to no yes yes yes yes
z/OS TCP/IP. ftp from z/OS to local
Linux

TN3270 from external LAN to z/OS no no maybec yes yes

ftp from z/OS to external LAN no no yesd yes yes

Externally assigned IP address needed no noe noe yes yes

for z/OS

Chapter 3. LANs and TCP/IP 43

 Characteristic 1 2 3 4 5

telnet connection to UNIX System no yes, only from yes, only from yes yes
Services base Linux base Linux

Browser connection from base Linux to no yes yes yes yes

z/OS

Browser connection from external LAN to no no maybec yes yes

z/OS

Browser or ftp connection from external yes yes yes yes yes
LAN to base Linux
a. The local 3270 sessions are based on LAN connections to Linux (to the aws3270 device
manager). The LAN connection is not to z/OS.
b. Only outgoing connections from z/OS to the external LAN may be used unless additional
iptables commands are used. The additional command functions are likely to require the use
of non-standard port numbers.
c. This would be an incoming connection and is not possible in the most basic iptables example.
Incoming connections may be accepted when an additional iptables setup is used.
d. This is an outgoing connection and may be used. A passive ftp connection may be needed.
e. The “locally fixed” IP address (10.1.1.2 in the examples) is not an assigned IP address.

The fundamental difference between scenario 3 and scenarios 4 and 5 is that the latter
require an assigned, fixed address for z/OS. Scenario 3 has complications for incoming
connections (from the external LAN) to z/OS, while 4 and 5 do not have this restriction. The
primary difference between 4 and 5 is where the external LAN interface appears; with
scenario 4 it is defined to z/OS; with scenario 5 it is defined in the base Linux.

3.4 Wireless connections

Wireless connections can be used by Linux TCP/IP or by OSA. We generally discourage the
use of wireless connections because they often do not provide the stability needed for
System z operation. Consider the following details:
򐂰 Linux typically sees a wireless connection as device ath0, wlan0, or eth0. The find_io
command lists a wireless interface along with Ethernet interfaces and associates a CHPID
with it. (The CHPID address for a wireless adapter is normally F8.) You can then use this
CHPID number as the path parameter for defining an awsosa interface.
򐂰 We cannot provide a cookbook for activating your wireless link for Linux, but you need to
have stable Linux wireless operation before trying to extend it to 1090 usage.
򐂰 We have noticed that the more recent Linux distributions (such as openSUSE 11.2, SLES
11, and Fedora 13) provide much more convenient wireless setup than earlier Linux
distributions.

3.5 Telnet to z/OS

If you elect to install the tunnel connection as described earlier (and as shown in the complete
example listed in the Appendix), you can connect from the base Linux to z/OS by both Telnet
(in line mode) or by a TN3270 client such as x3270. Using the IP addresses from our
examples, the Linux commands would be:
$ x3270 10.1.1.2 & (to start a TN3270 session via z/OS TCP/IP)
$ telnet 10.1.1.2 1023 (line-mode telnet session via z/OS TCP/IP)

44 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 The 1023 parameter in the telnet command specifies the port number that the AD-CD
TCP/IP and UNIX System Services profile use for Telnet connections. This port number
(1023) is not standard, and probably applies only to the AD-CD z/OS system.

3.6 Choices
Which 3270 connection mode is better? If only simple 3270 connections are needed (and not
more than 32 sessions are needed), then the use of basic aws3274 connections (shown in
scenario 1) is better. This is simpler to set up and does not require OSA or z/OS TCP/IP to be
configured or started.

Which CHPID mode should you use for OSA connectivity? QDIO mode has many
advantages for TCP/IP usage on a larger System z; it reduces the System z workload and
provides automatic sharing of the adapter across multiple LPARs. These considerations do
not fully apply to a 1090 system. The following points are relevant:
򐂰 QDIO operation offloads some processing from the 1090 CP to the Linux processor. The
offloading is not as much as on a larger machine, but it helps. It also reduces the number
of System z instructions needed to maintain LAN I/O operation. In informal operation we
noticed that ftp performance was about 20% faster with QDIO than with LCS.
򐂰 QDIO operation is only for TCP/IP; it does not handle SNA.
򐂰 QDIO can provide VSWITCH, IPv6, and Enterprise Extension connections.
򐂰 QDIO operation requires that OSA devices be defined in z/OS. These were not present in
AD systems prior to z/OS 1.8. The devices could be added to earlier AD systems, using
HCD to create a new IODF, or might be present in z/OS systems not derived from the AD
packages.
򐂰 Non-QDIO operation can mix TCP/IP and SNA (or handle just SNA or just TCP/IP).
However, SNA operation of the 1090 is not supported at this time.
򐂰 Suitable non-QDIO (LCS) devices have been defined in all the earlier z/OS AD systems.
(These are the CTCs starting at address E20.)
򐂰 The required OAT table is automatically updated when QDIO is used. The default OAT
table is probably satisfactory for non-QDIO TCP/IP usage and may be satisfactory for SNA
usage (although SNA is not supported at this time). The OSA/SF utility functions are used
(if needed) to manipulate the OATs.

Other than these points, there is no practical difference between using QDIO or non-QDIO on
a 1090 system. In particular, the user at a TN3270 TSO session cannot detect the difference.
Normal TCP/IP functions, such as ftp and Telnet, do not detect any differences. If you are
using recent AD systems (or another z/OS package with OSA devices defined) we suggest
you use QDIO mode because this represents the future direction for z/OS LAN operations.

3.7 Useful networking commands

The following commands may be useful when working with LAN devices:
z/OS operator commands:
D U,,,dddd,nn dddd = address, nn = number to display
D M=DEV(dddd) provides path status
D M=CHP display all CHPIDs defined to z/OS
D IOS,MIH display current MIH values

Chapter 3. LANs and TCP/IP 45

 SETIOS MIH,DEV=E201,TIME=00:30 example of setting MIH
TSO commands:
NETSTAT DEV display all devices and links
NETSTAT HOME display home address
NETSTAT GATE display gateway addresses
NETSTAT CONN display connection status
TRACERTE ipaddress
PING ipaddress
(Issue ALLOC DD(SYSTCPT) DA(*) before TRACERTE or PING for more data.)
VTAM commands:
V NET,ACT,ID=LCL701 vary local 3270 active to VTAM
D NET,MAJNODES display major nodes
D NET,ID=xxxxxx,E display information about specific node
D NET,TRL list the TRLEs
D NET,TRL,TRLE=OSATRL1E data about specific TRLE
V NET,ID=OSATRL,ACT activate a major node
V NET,ID=OSATRL,INACT
V NET,ID=ISTTRL,ACT,UPDATE=ALL remove inactive TRLEs from TRL list

It is important to note that the name LCL701 in the sample V NET command is the VTAM
name of the terminal. This name is not related to the LUname specified in the 1090 devmap.
A 3270 session has both an aws3274 LUname (specified in the 1090 devmap) and a VTAM
name (specified in VTAMLST). Basic MVS operator consoles are not specified in VTAM and
have no VTAM name. This terminology is unfortunate because the aws3274 LUname (used to
link a TN3270e session to an aws3274 definition) is not necessarily the same LUname
associated with a VTAM operation.

Note that zPDT does not support the VMAC function from z/OS. The only virtual mac
supported is generated on z/VM with the layer-2 vswitch.

46 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 4

Chapter 4. Using basic zPDT commands

The full set of zPDT commands, with their syntax, is listed in Volume 1 of this series. This
chapter illustrates use of the more common commands.

1090 commands fall into several categories:

򐂰 Setup commands, typically used when the 1090 is not operational.
򐂰 Basic operation commands, to start the 1090, IPL a system, and later stop the 1090.
򐂰 CP commands for low-level operations such as displaying System z memory.
򐂰 Miscellaneous commands.

All of these commands are Linux executable files. The operational commands must be used
under the same Linux userid that started 1090 operation. Only one 1090 instance may be
started by a given userid and the commands assume they are to work with that instance. (The
setup commands are not directly related to a running 1090 and can be used by any Linux
userid that can access them.)

© Copyright IBM Corp. 2009, 2011. All rights reserved. 47

4.1 Setup commands
The following commands (with operand examples) are typically used when the 1090 is not
operational. The awsckmap command may be used after changing a devmap. It simply verifies
that the devmap is in the correct format. It does not verify that files are in the correct emulated
format.
$ awsckmap aprof1 check devmap
$ awsckmap /bill/map123.txt can specify a full path name
$ awsckmap aprof1 --list long list

An emulated disk volume must be created before it can be used by the 1090. The alcckd
command creates 3380 or 3390 volumes. There are four standard-size 3390 volumes
(3390-1, -2, -3, -9) that can be created by specifying the full model type. Otherwise the -s
parameter may be used to specify the number of cylinders to create.1 The emulated volume
contains only the effective cylinders; diagnostic and alternate cylinders are not emulated.
$ alcckd /z/WORK01 -d3390-3 create emulated 3390-3 volume
$ alcckd /z/WORK02 -s9000 -d3390 create volume with 9000 cylinders
$ alcckd /z/WORK03 -d3390-1 -z create and zero the volume

The alcckd command does not place any software blocks (label, VTOC) on the volume. The
user must do this later, using operating system utilities.

The find_io command (which has no operands) is used to list Ethernet interfaces and their
associated CHPID number (relevant only for interfaces used for OSA Express emulation).

The z1090ver command may be used to determine the version of the 1090 that is being used.
The z1090instcheck command may be used to partly verify that the Linux environment is
correct for the 1090.

4.2 Basic operation

These two commands start and stop 1090 operation. In the example, the devmap (file name
aprof1) is in the current directory; otherwise, a complete path name would be used.
$ awsstart aprof1 start 1090 operation2
$ awsstart aprof --clean erase old 1090 logs/traces/dumps
$ awsstop stop 1090 operation

The awsstop command instantly ends System z operation. No warning is sent to the System z
operating system. We recommend that the System z operating system be stopped normally
(whatever this may mean for various operating systems) before issuing awsstop.

The token command may be used to verify that the hardware key is available to the 1090.
This command works only when the 1090 is running.

The ipl command performs the architected System z IPL operation. It must point to a device
that has a suitable IPL program installed. This is normally the operating system residence
device but could be a disk or tape that contains a stand-alone System z program. The use of
an IPL parameter is completely dependent on the operating system involved and how the

1
Specifying more than 65520 cylinders creates an EAV volume. You should verify that your System z operating
system supports these before creating one.
2 The earlier versions of awsstart required the characters “--map” before the devmap name. This is now optional.

48 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
parameter is configured for that instance of the operating system. The 1090 environment
must be initialized (via awsstart) prior to issuing the IPL command.
$ ipl 560 simple IPL
$ ipl A80 parm 0A82CS IPL with parameter

The awsmount command is used while the 1090 is running. It displays or changes the
emulated device file associated with an emulated device. The first example is equivalent to
mounting a tape on the device at address (device number) 560. This function makes the
device ready and sends the appropriate attention interrupt to the operating system. This
command is not limited to emulated tape drives, although that is the most common use. It can
also be used for emulated disk drives or an emulated printer.
$ awsmount 560 -m /z/mytape mount volume when none is mounted
$ awsmount 560 -o /z/tape05 mount another volume, replacing old
$ awsmount 560 -q query device file status
$ awsmount 560 -s rewind emulated tape
$ awsmount 560 -x rewind and unload emulated tape

If a file name is mounted as an emulated tape and that file does not already exist, it is
automatically created by the awsmount command. You must be careful when typing the file
name in an awsmount command to ensure that you specify the correct name and directory. For
example, suppose you intended to mount and write to an existing emulated tape,
/tape/oldtape1, but instead typed:
$ awsmount 560 -m oldtape1

This would allocate a new awstape file named oldtape1 in your current directory. If you then
write a large amount of data to this file, it can fill your /home file system and possibly cause
problems. z/OS’s label processing routines will catch some of these problems, but not all, so
you should always be careful to use the correct names.

Files mounted with awsmount must be appropriate for the device, of course. A file mounted on
an emulated tape drive must be in awstape format. (For an emulated tape drive opened for
output, a new awstape file is automatically created if necessary.) A file mounted on an
emulated 3390 disk drive must be in awsckd format. None of these formats are standard
Linux formats; the emulated disk device files must be created with 1090 utilities. Emulated
tape files (awstape) are created by writing to an emulated tape drive, mounted with the
awsmount command.

The awsstat command provides the status of emulated I/O devices, including the Linux file
name mounted on the device and (for disks) the last track used.
$ awsstat query status of all emulated devices
$ awsstat 0A80 0A82 query status of specified devices
$ awsstat -i2 0a82 display status every 2 seconds

The display output from awsstat is wide; it is best to widen the Linux window to almost full
width before using awsstat. An example of the command is as follows:
$ awsstat A82
Config file: /ibmsys1/aprof1
DevAdr Subch ---Mgr-- Actv Busy --PID-- -----Device Information----------
0A82 15 AWSCKD Yes No 4329 Cyl-368, Head-10 /z/S7SYS1

Most of the output has obvious meanings. The Subch (subchannel) is an internal detail and
the PID (Linux process id) is not normally needed. The DevInfo field shows the current logical
position in the device.

Chapter 4. Using basic zPDT commands 49

 The awsin command sends input to an emulated 3215. z/OS does not use 3215 devices but
they are sometimes used by other operating systems. If only one 3215 is defined then the
device number (009 in this example) need not be entered (unless the data element starts with
a numeric digit; in this case the device number must be entered).
$ awsin 009 'This is input' assume 3215 address 009
$ awsin 'This is input' if only one 3215 defined

The oprmsg command sends input to the “hardware console” or “HMC console”, or “SCLP
operator message interface.” This is the interface used by z/OS, for example, when all the
normal z/OS consoles have been lost. There is no device address associated with this
interface.
$ oprmsg 'V CN(*),ACTIVATE' send message to z/OS

1090 commands function as Linux commands, and are entered through a shell prompt. The
operands must conform to Linux shell rules. Some characters, such as dollar sign ($), right
parenthesis), and left parenthesis (, have special meanings when entered as part of a
command through a shell. It is necessary to escape these characters. This can be done by
placing single quotes (' ‘) around the whole operand or by placing a backslash (\) before
each special character.

The ready command generates an asynchronous device end for the indicated emulated
device. This is typically associated with mounting a new volume on the device.
$ ready 590

The ipl_dvd command emulates the operation of using an IPLable DVD in an HMC. Some
software, such as z/VM, is distributed in this way.
$ ipl_dvd /media/530_GA_3390_DASD_DVD/cpdvd/530vm.ins

The file name used with ipl_dvd must be in the correct .ins format, which is similar to an OMA
control format. Our particular example involves VM and this may not work without the HMC
function because this mode of VM installation uses unique HMC 3270 functions. Some Linux
distributions may be packaged for DVD installation.

Search paths
Our examples use a parameter on the awsstart command to specify the devmap. There are
other ways to find these files. The complete search algorithms, in the order used, are as
follows:

To find the devmap:

Use the file named in the awsstart parameter, if specified.
Use the CONFIG_FILE environment variable, if it exists.
Use file devmap.txt in the current directory, if it exists.
Use /home/<userid>/z1090/configs/devmap.txt, if it exists (not recommended).
Error, if none of the above exist.

4.3 CP commands
The following commands control operation of the 1090 System z processors, known as CPs.
The first (or only) processor is CP number 0. A second processor (if it exists) is CP number 1,
and so forth. By default, these commands are sent to CP 0. The cpu command may be used

50 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
to specify a different default processor. These commands can also be directed to zIIPs,
zAAPs, and IFLs which are assigned cpu numbers as though they were CPs.
$ cpu 1 specify default processor
$ stop stop indicated (or default) processor
$ start 1 start indicated (or default) processor
$ restart 0 perform CP restart function
$ query 0 query indicated processor
$ interrupt 0 send external interrupt
$ storestatus
$ sys_reset perform System z reset
$ storestop 1AC0 stop on store in absolute address

$ adstop 1AC0 on set an address stop at indicated address

$ adstop 1AC0 off remove the address stop
$ memld <file name> address load Linux file into System z memory
$ loadparm 0a8200 set SCLP IPL parm (for SCLP usage only)
$ loadparm -d display SCLP IPL parameter
$ tracem control interrupt trace

The following display and change commands are best used when the CP is stopped.
Addresses specified for the adstop, d, and st commands are real addresses or virtual
addresses, depending on how the address is written:
address 1AC0 real memory address3
address v1AC0 virtual memory address (primary AS)
address vh1AC0 virtual memory address (home AS)
address vs1AC0 virtual memory address (secondary AS)

$ d v1AC0 64 display 64 bytes from address 1AC0

$ d 1AC0.40 display x’40’ bytes (real address)
$ d t vh1AC0 32 display, including EBCDIC
$ st v1AC0 47F01CD0 modify memory value at address v1AC0

$ d psw display psw for current mode

$ st psw FF007AB0 0 0 123456 set 128-bit PSW

$ d g display general registers

$ d g3 display general register 3
$ st g1 1234 store x’00001234’ in 32-bit register
$ st gx1 1234 store x’0000000000001234’ in 64-bit reg

$ d y display floating point registers

$ d y3 display floating point register 3
$ st y1 1234567887654321 store x’1234567887654321’ 64-bits

$ d z display access registers (always 32-bits)

$ st z3 ABCD store x’0000ABCD’ in access register 3

$ d x display control regisers

$ st x1 AABBCCDD store 32 bits in control register 1
$ st xx1 AABBCCDD store 64 bits (x’00000000AABBCCDD’)

$ d r display architecture mode

3
By “real memory address” we mean an address in System z memory. The “real address” is not translated through
the System z virtual memory process.

Chapter 4. Using basic zPDT commands 51

 $ d yc display floating point control register
$ d pfx display prefix register

The following conventions are used for the display and store commands:
򐂰 The display storage commands take the specified address and round it downward to the
nearest 32-byte (hex 20) boundary.
򐂰 Memory display commands display 32 bytes (in hex) per line. If the t parameter is used,
EBCDIC is also displayed at the end of each line. In either case, the lines are long and the
Linux window used should be wide.
򐂰 Store commands for memory work in bytes, starting at the address specified in the st
command.
򐂰 Registers are displayed as 64-bit registers when in z/Architecture mode and 32-bit values
when not in z/Architecture mode.
򐂰 Store commands (memory and registers) assume data is in hex.
򐂰 Store commands for registers work in 32-bit words (st g commands) or 64-bit words (st
gx commands). Data is padded on the left with zeros.
򐂰 Memory displays include the storage protection key (displayed after the hex data).
򐂰 PSW values (st psw xxx) are entered as 32-bit words. Changing a 128-bit PSW means
that four operands are needed. The command st psw 123 456 789 ABC places
x’00000123’ in the first word of the PSW, x’00000456’ is intended for the second word (but
the second word is forced to zeros), x’00000789’ is placed in the third word, and
x’00000ABC’ is placed in the last word.
򐂰 If a storage word operand overflows (for a register or segment of the PSW) the value is set
to x’FFFFFFFF’.
򐂰 Floating point registers are always treated as 64-bit words.

A memld command might be:

$ memld /home/ibmsys1/initrd 800000

This would read the contents of the indicated Linux file into the System z memory, starting at
real address (hexadecimal) 800000.

4.4 Devmaps
A devmap must exist when starting 1090 operation. The devmap defines the size of System z
memory and several other parameters. It also specifies which device managers to start and
what emulated devices are connected to each device manager. Many devmaps may exist;
they are simple Linux text files. Only one devmap can be used when starting a 1090 instance
and it cannot be dynamically changed while the 1090 is running.

Typically, zPDT users have a number of devmaps for a variety of purposes. For example:
򐂰 A devmap for the current z/OS release, with only the basic IPL volumes and no OSA
򐂰 A devmap for the current z/OS release, with all the volumes that have been installed and
with one or two OSAs (depending on the LAN and tunnel environment desired)
򐂰 A devmap for a previous z/OS release (using the normal AD-CD device numbers)
򐂰 A devmap contains both the current AD-CD release (using the normal device numbers)
and a previous release (using other device numbers)
򐂰 A devmap for basic z/VM

52 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
򐂰 A devmap for z/VM and one (or two) z/OS releases

Appendix A, “z/OS 1.12 AD-CD example” on page 61 provides an example of a complete

devmap, along with the z/OS TCP/IP setup required for both LAN and tunnel usage.

Chapter 4. Using basic zPDT commands 53

54 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 5

Chapter 5. Frequently asked questions

The following FAQs are more specific to installation and detailed usage. Volume 1 of this book
series contains additional FAQs that are more related to initial zPDT concepts.

Q: Can I use any Linux userid instead of ibmsys1?

A: You can use any Linux userid for zPDT provided it is not longer than eight characters. You
should use the same userid for all zPDT installations and operations.

Q: You say that Ethernet SNA operation is not supported. Might it work?
A: Yes, it might. It has not been tested and IBM will not respond to problems using it.

Q: Can I use a SCSI DLT tape drive?

A: It should work (provided it supports the SSC-3 SCSI Command Set for Sequential
Devices), although this is not supported by IBM and has not been tested.

Q: The 1090 token does not work on my new laptop. What might be the problem?
A: At the time of writing (February, 2011) the current Linux releases used with zPDT
apparently did not fully support USB3 ports. Some laptops have both USB2 and USB3 ports;
try using the USB2 port.

Q: Can I use a SCSI 4 mm tape drive?

A. It might work but we strongly suggest you do not use 4 mm drives. These have proven to
be poorly suited for emulated S/390® work.

Q: Will using a zIIP or zAAP or IFL increase the performance of my 1090?

A: No, assuming you are replacing a CP with the zIIP or zAAP. These specialty processors
operate at the same speed as a “normal” 1090 CP. They are provided to allow developers to
verify that their applications use a zIIP or zAAP or IFL in the intended manner. It is possible
they could improve performance through parallel operation with the base CP.

Q: Is the floating point hardware of the base machine used when executing System z floating
point operations?
A: Sometimes. This is a complex area when floating point exception conditions are
considered and IBM has not disclosed the 1090 design for this area.

Q: Why do you not provide a definite MIPS value? This would help us determine how to best
use the 1090.

© Copyright IBM Corp. 2009, 2011. All rights reserved. 55

 A: There are no definite numbers. A MIPS measurement is very dependent on the exact
workload. The approximate ranges we sometimes discuss for the 1090 assume a traditional
commercial application mix, although even this is difficult to define exactly.

Q: Why are there warnings about running beagle in a 1090 system?

A: Beagle attempts to index the contents of the file systems. A typical 1090 has a number of
emulated 3390 volumes containing mostly EBCDIC and executable data sets. From a Linux
viewpoint, these are very large binary files and attempts to index them can lead to excessive
processor usage by beagle or similar programs. This problem seems to have mostly
disappeared with recent Linux distributions.

Q: Can I have multiple tap (tunnel) interfaces, such as tap0, tap1, and so forth?
A: Yes, starting with the zPDT release in spring 2010. A total of four OSA devices of any type
may be defined. The tunnel interfaces will typically have CHIPD numbers A0, A1, A2, and A3.
The tap devices may be defined (as seen by the find_io command), but they are not used
unless a corresponding OSA device exists in the devmap.

Q: Can I run multiple TCP/IP stacks on a single emulated OSA-Express adapter?

A: Yes.

Q: Can I place emulated 3390 volumes on an NFS server?

A: In principle, yes. However, access time must remain within the tolerance that z/OS expects
for disk activities. In general, we do not think this is a good idea. (If any I/O operation takes
more than 30 seconds, the 1090 device manager is considered dead and is restarted. z/OS
has internal timers with much shorter timeouts than 30 seconds.)

Q: Can I share emulated volumes on an NFS server with several 1090 machines?
A: No. This would almost certainly result in corrupted data unless the NFS files are read-only
files. Such usage might be practical for awstape files.

Q: My OSA interfaces do not start and I receive error messages that SIOCGIFINDEX failed.
What is this?
A: This seems to occur mostly with openSUSE 10.3. If you run the find_io command, you
will probably see that the LAN interfaces do not have MAC addresses. We do not know
exactly what triggers this problem, but we find that updating openSUSE 10.3 (using the online
update function that is part of the Linux system) often resolves the problem. We suspect that
the support levels for particular models of Ethernet adapters may be the cause.

Q: Why might I need to specify a unit address in the device statements for OSA? I do not
understand these.
A: A full discussion is beyond the scope of this document. For TCP/IP, you need to ensure
that the unit addresses associated with non-QDIO TCP/IP usage are 0 and 1. (This is
required by the default OAT used by OSA.) You need to ensure that unit address FE is used
only for OSA/SF when using the default OAT. You need to remember that the default unit
address is the same as the low-order two digits of the device number (“address”). Provided
you meet these requirements there is no need to specify a unit address in the device
statements for OSA. For QDIO operations you should not need the unit address operands.

Q: Does zPDT support thin interrupts?

A: Yes, for OSA devices and cryptographic emulation. (This function is properly known as the
Adapter Interrupt Facility.)

Q: Can I filter IP traffic before it is sent to my emulated OSA-Express interface? This reduces
the overhead involved in rejecting packets not addressed to my system.
A: In OSD (QDIO) mode there is some automatic filtering. In OSE (non-QDIO) mode you can
customize the OAT with your IP address. If this is done, the OSA interface will pass only
packets intended for this IP address. If this customization is not done (and it is not done in the

56 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
default OAT) then all packets are sent to the host TCP/IP and unwanted packets are rejected
at that level. If you use NAT functions on the base Linux, then most of the filtering is done at
that level.

Q: Is OSA-Express emulation different than OSA emulation?

A: Yes, very much so, although OSA operation of simple TCP/IP can usually be provided by
OSA-Express without changes to the System z operation. (This question is related to a
terminology problem and assumes that OSA means the original OSA adapter, which
operated largely as an LCS device.)

Q: Is OSN operation (CDLC) provided with OSA-Express2 emulation?

A: No.

Q: Does OSA-Express2 emulation support jumbo frames? With QDIO? With non-QDIO?
A: Jumbo frames are not supported by zPDT with QDIO, although some users have been
successful using them. Appropriate kernel parameters are needed as specified in “Notes for
sysctl values” on page 11.

Q: Should I use 1492 or 1500 as the maximum packet size (MTU) when using awsosa?
A: Use a maximum of 1492. The details are beyond the scope of this document. (As best we
can tell, the System z communication routines automatically adjust this number down if
necessary. Thus it probably does not matter whether you specify 1492 or 1500.)

Q: I want to use the OSA Express function with QDIO, but my z/OS does not have any OSA
devices defined. How do I add them to z/OS?
A: This is done with the HCD utility under z/OS, creating a new IODF. Extensive IBM
documentation exists for HCD. An example is included in the third book in this series
(GA24-7723).

Q: Does QSA-Express emulation include advanced functions such as VIPA?

A: Yes, when using QDIO.

Q: Can I use a continuing range of addresses (device numbers) when I have multiple OSA
QDIO interfaces? For example, 400-402 for TCPIP1, 403-405 for TCPIP2, and so forth.
A: No. For z/OS we believe the first OSA address (for a TCP/IP stack, in this example) must
be an even number. You would need to use 400-402, skip 403, then use 404-406, skip 407,
and so forth. (This statement may not be correct for z/VM.)

Q: Do the OSA-Express2 offload functions work? Do they accomplish anything on an

emulated system?
A: The Linux-based 1090 OSA implementation does not use offload functions at this time. In
some cases (with the latest Linux kernels) you may need to force Linux to disable offloading.

Q: What PC Card (PCMCIA-type card) should I use for additional Ethernet ports on a
ThinkPad?
A. Use any card that the base Linux system accepts. We tested with an Xterasys Gigabit PC
Card (98-012084-585). We also informally tried several older IBM 10/100 Etherjet <<
Ethernet? >>cards.

Q: Can I use IP aliasing in Linux while using the 1090?

A: Yes, but only when using zPDT release 39.16 or later.

Q: The find_io command indicates a MAC address of 0:0:0:0:0:0 for the tap0 interface. Can
a MAC address be zeros?
A: This is normal for the tap interfaces. A “real” LAN adapter should not have a zero MAC
address.

Chapter 5. Frequently asked questions 57

 Q: I have multiple Ethernet adapters, each on a different subnet. Response is very slow and I
get multiple responses to pings. Is there a problem using multiple adapters?
A: In general, no. However, multiple interfaces on different subnets should not be connected
to the same VLAN. This creates routing, ARP, and duplicate response issues. Also, the
external routing configuration (external to your system) may produce multiple responses.
Multiple subnets on a single physical network may produce multiple responses.

Q: I have an error message about GVRP when I try to use a VLAN/VSWITCH in z/VM. Is this
supported:
A: No, GVRP is not supported. You should specify NOGVRP for your VSWITCH.

Q: Why do some AD-CD releases pause for many seconds while shutting down?
A: You can edit the SHUTDOWN entries in PARMLIB to remove or change any pause
statements.

Q: I am using z/VM and have a problem with MONITOR. Does the 1090 support this usage?
A: An APAR fix for z/VM 5.2 and 5.3 is available to resolve this problem. It is APAR VM64385.

Q: You are inconsistent with the addresses for the AD-CD volumes. For example, sometimes
volume SARES1 is at address A91 and sometimes at address AA0. Which is correct?
A: Both are correct. Any 3390 volume can be at any address that is defined as a 3390 in the
IODF for that z/OS system. For ease of documentation we always show the IPL volume at
A80 and the SYS1 volume (which contains the IODF and IPLPARM datasets) at A82, but
these addresses are not required. The IPL address and parameter much match the
addresses you use, of course.

Q: What happens if I remove the hardware key?

A: The 1090 will stop after a while.

Q: You use userid ibmsys1 throughout all the examples. Is there something special about this
userid?
A: No.

Q: Is there any national language support in the 1090?

A: No.

Q: Can I use an alternate translation table to convert EBCDIC to ASCII for awsprt output?
A: No.

Q: Can I use multiple 1090 tokens to obtain more CPs?

A: Yes, if you have a “1090” token. No, if you have a “1091” (RDzUT) token.

Q: I have several Linux windows open while running the 1090. I can enter 1090 commands in
any window, which is convenient. However, I also sometimes get output messages in a
different window from where I entered a command. Is this normal?
A: Yes. 1090 output messages (but not command output messages) are sent to the console
session that issued the awsstart command.

Q: My z1090 rpm installation failed with an error message about db_recovery. What now?
A: Try the command rpm --rebuilddb and then install z1090 again (using the z1090 installer
program, of course, and not trying to directly install the z1090 rpm).

Q: Can I routinely migrate to the next Linux releases when they become available?
A: Maybe. There is no unique 1090 tie to a particular release. However, it is possible that the
1090 installation steps might not work for a new release (due to different library paths) or that
the new release might not support the particular hardware in your base machine. IBM support
exists only for the recommended release(s).

58 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
Q: I am using an emulated printer and this sends output to a Linux file. Does this file remain
open for output by the 1090 all the while the 1090 is running?
A: Yes. It is closed if you use awsmount to assign a new output file for the printer.

Q: Is there an easy way to delete all the existing disk partitions when installing openSUSE?
A: Yes, delete the /dev/sda entry. This does not really delete the hard disk, but it does delete
all partitions on it.

Q: Can emulated printer output be directed to /dev/lp0 or something similar?

A: We do not know; this was not tested.

Q: I installed a different HDD in my T60 ThinkPad and now I cannot boot from CD or HDD.
A: You may have installed the new HDD upside down. It is easy to do.

Q: You provide very explicit Linux component lists in your examples. Can I include more
packages?
A: Yes. We routinely include the C/C++ compiler, for example, although it is not needed for
the 1090.

Q: Does the 1090 operate in kernel mode? In suid mode?

A: Kernel mode is not used, but one module (part of awsosa) operates in suid mode.

Q: How do I add more SUSE components after I have completed the basic installation?
A: Application  System  Yast  Software Management  Filter: Package Groups
and then follow the installation prompts. The exact navigation changes with new distributions,
but the general idea remains the same.

Q: You specified that userid ibmsys1 should be a member of group zpdt. Is this needed?
A: No. However, it is useful for additional Linux security measures as described in the third
book in this series (SG24-7723).

Q: Are 1090 commands case sensitive? Can I issue ipl or IPL?

A: The commands are case sensitive. They are simply the names of Linux files and Linux file
names are case sensitive.

Q: Can I run as root when installing and using the 1090?

A: No. Follow the instructions concerning when to work as root and when to work under a
normal userid (such as ibmsys1).

Q: The z1090instcheck command does not work or gives the wrong results. Why?
A: You may need the full path name for the z1090instcheck command in some cases. Your
PATH may be pointing to a down-level version at the time you issue the command. Also, you
must have installed the 1090 code before you can use this command.

Q: I have a SCSI tape drive. I want to use it directly for Linux functions (not directly connected
with 1090 operation) but I cannot find the mt command (a “standard” Linux command for
manipulating tape devices).
A: We noticed that mt is not always installed with some Linux distributions. In some cases it
appears to be part of the cpio rpm. For 64-bit RHEL 5.2, we needed to install
mt-st-0.9b-2.2.2.x86_64.rpm to obtain the mt command.

Q: Does the 1090 handle 3270 nulls correctly?

A: This is not a function of the 1090; it is a function of the 3270 emulator and, to some extent,
the application involved. Relevant functions for x3270 can be found in Options  Toggles 
Blank Fill. The ISPF command nulls on|std|all|off may be relevant.

Chapter 5. Frequently asked questions 59

 Q: Does IBM need to enable something to allow full operation of the five CRYPTO
instructions?
A: No, full operation is always enabled.

Q: How can I write a tape mark on an AWSTAPE volume?

A: Use awsmount xxx --wtm where xxx is the address (device number) of the tape drive.
Notice there is a double dash before the wtm option.

Q: Where do I obtain OMA distributions?

A: We do not know of any IBM products currently distributed in OMA format. Some Linux for
System z distributions may be in this format.

Q: Should device statements (in a devmap) be in order by addresses?

A: No particular order is needed.

Q: I want to use PCOM instead of x3270. Is this acceptable? Can you include it with the 1090
package?
A: Yes. However, you should use a release later than PCOM 5.5. We have verified that
version 5.5 is not suitable for the 1090. PCOM is part of a separate IBM product. We cannot
include it as part of the 1090 package.

Q: I installed the recommend Linux on my T61p ThinkPad, but I cannot access the token (or a
USB disk drive).
A: It appears that USB usage may be sensitive to BIOS levels. In at least one case, updating
the T61p to the current BIOS level (which was 2.09, at the time this was noticed) solved the
problem.

A: The AD-CD system always starts TCP/IP and associated jobs. How can I delete them?
Q: You can edit the VTAMAPPL types of entries in PARMLIB and remove the associated
commands. While running z/OS you can issue P TCPIP, wait a few seconds, and then issue
C INETD4.

Q: Can I use RMF?

A: Yes, but not all of it is relevant on a 1090 system.

Q: I have volumes at addresses A80 through A8F. Do I need to define a new awsckd unit in
order to add more disk volumes?
A: No, you can have up to 256 volumes in one instance of awsckd.

Q: I am using the IBM Personal Communications product to connect from a remote PC to

z/OS running on the 1090. Every time I start Personal Communications it wants to print
something. How can I stop this?
A: This is a well-known issue, and is not related to the 1090. Personal Communications
stores user profiles in .ws files (such as bill.ws, for example). Find the .ws profile you are
using and add the following lines at a reasonable place in the profile:
[LT]
IgnoreWCCStartPrint=Y

Q: Can I make the kernel.shmmax value very large to avoid worrying about it?
A: As far as zPDT is concerned, you could do this. However, it is possible that other Linux
applications might accept the very large value and attempt to use unreasonable amounts of
shared virtual memory, resulting in excessive paging.

60 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 A

Appendix A. z/OS 1.12 AD-CD example

We installed AD-CD z/OS 1.12 AD, including all the volumes present on the DVDs. We used
the single ThinkPad Ethernet adapter for OSA connectivity and configured it for QDIO mode.
This appendix describes our specific definitions. Although this material applies only to the
z/OS 1.12 AD system, it may be helpful when setting up other environments.

The examples we use assume a machine with modest memory (4 to 8 GB). A machine with
larger memory would probably have larger root and swap partitions.

© Copyright IBM Corp. 2009, 2011. All rights reserved. 61

A.1 Disk planning
All the 3390-3 volumes in the 1.12 release require about 87 GB of disk space. (It is very
unlikely that many users would elect to install all the volumes. Four volumes are needed to
IPL; all the others are optional, depending on your usage plans.) We also had two 3390-1
volumes with local data. This made a total of about 90 GB for emulated disk volumes.

Our Linux base was installed in a single 12-GB partition, and we created a 4-GB Linux swap
partition.

A.2 Connectivity planning

We had a single Ethernet adapter in the T61p. For our LAN setup we used Scenario 4
described earlier. This scenario includes a tunnel OSA connection between the base Linux
and z/OS, plus an OSA LAN connection from z/OS to the outside world. We also used
aws3274 connections (which appear as local, channel-attached devices) for the MVS console
and simple VTAM terminals. The TCP/IP connectivity is as follows:
򐂰 The IP address for the base Linux (from external connections on a router/hub) is
192.168.0.80. This IP address cannot be accessed from z/OS.
򐂰 The IP address of z/OS (from external connections on a router or hub) is 192.168.0.81.
This IP address cannot be accessed from Linux. (This is not a valid IP address for
connection to the Internet; you must provide your own fixed IP address.)
򐂰 The IP address for internal connections to Linux TCP/IP (from the x3270 sessions, for
example) is 127.0.0.1; this is the default localhost address for Linux.
򐂰 The IP address used to access z/OS from Linux (via tunnel) is 10.1.1.1.
򐂰 The IP address used to access Linux from z/OS (via tunnel) is 10.1.1.2.
򐂰 The IP address of the router is 192.168.0.1; this is the default route for z/OS (and Linux).

A.3 Listings
We used the find_io command to determine that our Ethernet adapter was eth0, and that it
was assigned as CHPID F0. (As a practical matter, the integrated Ethernet adapter is always
assigned to CHPID F0.) The tunnel interface is always CHPID A0. We elected to use the
QDIO mode for both OSA interfaces., We used the following devmap:
[system]
memory 3000m
3270port 3270
processors 2

[manager]
name aws3274 0002
device 0700 3279 3274 mstcon
device 0701 3279 3274 tso
device 0702 3279 3274 tso
device 0703 3279 3274 tso

[manager]
name awsckd 0001
device 0A80 3390 3990 /z/ZCRES1
device 0A81 3390 3990 /z/ZCRES2
device 0A82 3390 3990 /z/ZCSYS1

62 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 device 0A83 3390 3990 /z/ZCUSS1
device 0A84 3390 3990 /z/ZCPRD1
device 0A85 3390 3990 /z/ZCPRD2
device 0A86 3390 3990 /z/ZCPRD3
device 0A87 3390 3990 /z/ZCDIS1
device 0A88 3390 3990 /z/ZCDIS2
device 0A89 3390 3990 /z/ZCDIS3
device 0A8A 3390 3990 /z/ZCDIS4
device 0A8B 3390 3990 /z/ZCDIS5
device 0A8C 3390 3990 /z/ZCDIS6
device 0A8D 3390 3990 /z/ZCDB91
device 0A8E 3390 3990 /z/ZCDB92
device 0A8F 3390 3990 /z/ZCDB93
device 0A90 3390 3990 /z/ZCDB81
device 0A91 3390 3990 /z/ZCDB82
device 0A92 3390 3990 /z/ZCDB83
device 0A93 3390 3990 /z/ZCDB84
device 0A94 3390 3990 /z/ZCCI31
device 0A95 3390 3990 /z/ZCCI41
device 0A96 3390 3990 /z/ZCWAS1
device 0A97 3390 3990 /z/ZCWAS2
device 0A98 3390 3990 /z/ZCWAS3
device 0A99 3390 3990 /z/ZCIMS1
device 0A9A 3390 3990 /z/ZCIMS2
device 0A9B 3390 3990 /z/ZCIMS3
device 0A9C 3390 3990 /z/ZCBBN1
device 0A9D 3390 3990 /z/ZCBBN2
device 0A9E 3390 3990 /z/SARES1
device 0AA0 3390 3990 /z/WORK01 #local volumes, not part of AD-CD
device 0AA1 3390 3990 /z/WORK02

[manager]
name awsosa 0019 --path=A0 --pathtype=OSD --tunnel_intf=y
device 400 osa osa
device 401 osa osa
device 402 osa osa

[manager]
name awsosa 0009 --path=F0 --pathtype=OSD
device 404 osa osa
device 405 osa
device 406 osa osa

[manager]
name awstape 004
device 581 3490 3490

[manager]
name awscmd 1000
device 580 3490 3490

No modifications or definitions are needed in Linux to define the tunnel interface. This
interface (and associated IP address) does not exist until awsstart is issued, using a devmap
that contains the tunnel_intf operand in an awsosa definition.

Appendix A. z/OS 1.12 AD-CD example 63

 QDIO operation requires a TRL major node in VTAM. This is provided by member OSATRL1
in ADCD.Z112.VTAMLST in the AD system, which we changed slightly. (The TRL member
name is included in the list in member ATCCON00). The continuation characters (the X
characters) are in column 72.
OSATRL1 VBUILD TYPE=TRL
OSATRL1E TRLE LNCTL=MPC,READ=(0400),WRITE=(0401),DATAPATH=(0402), X
PORTNAME=PORTA, X
MPCLEVEL=QDIO
OSATRL2E TRLE LNCTL=MPC,READ=(0404),WRITE=(0405),DATAPATH=(0406), X
PORTNAME=PORTB, X
MPCLEVEL=QDIO

We need both TRLEs only when using two OSA definitions, of course.

We used the following TCP/IP profile in z/OS. (If using the z/OS AD-CD system, be certain to
update the correct PROFILE. In the z/OS 1.12 AD system this is member PROF1.)
ARPAGE 5
DATASETPREFIX TCPIP

AUTOLOG 5
FTPD JOBNAME FTPD1 ; FTP Server
PORTMAP ; Portmap Server
ENDAUTOLOG

PORT
7 UDP MISCSERV ; Miscellaneous Server
7 TCP MISCSERV
9 UDP MISCSERV
9 TCP MISCSERV
19 UDP MISCSERV
19 TCP MISCSERV
20 TCP OMVS NOAUTOLOG ; FTP Server
21 TCP OMVS ; FTP Server
23 TCP TN3270 ; Telnet Server
25 TCP SMTP ; SMTP Server
53 TCP NAMESRV ; Domain Name Server
53 UDP NAMESRV ; Domain Name Server
69 UDP OMVS ; OE TFTP SERVER
80 TCP OMVS ; OE WEB SERVER
111 TCP PORTMAP ; Portmap Server
111 UDP PORTMAP ; Portmap Server
135 UDP LLBD ; NCS Location Broker
161 UDP OSNMPD ; SNMP Agent
162 UDP SNMPQE ; SNMP Query Engine
433 TCP OMVS ; OE WEB Server
443 TCP OMVS ; Secure Server
512 TCP RXSERVE ; Remote Execution Server
513 UDP OMVS ; OE RLOGIN SERVER
514 UDP OMVS ; OE syslog server
514 TCP RXSERVE ; Remote Execution Server
515 TCP LPSERVE ; LPD Server
520 UDP OROUTED ; RouteD Server
580 UDP NCPROUT ; NCPROUTE Server
750 TCP MVSKERB ; Kerberos
750 UDP MVSKERB ; Kerberos

64 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
 751 TCP ADM@SRV ; Kerberos Admin Server
751 UDP ADM@SRV ; Kerberos Admin Server
; 1021 TCP OMVS ; OE FTP SERVER
1023 TCP OMVS ; OE TELNET SERVER
1023 UDP OMVS ; OE TELNET SERVER
1024 TCP OMVS ; OE SERVICES
1415 TCP CSQ1CHIN ; CSQ1 MQ TCP Listener
3000 TCP CICSTCP ; CICS Socket
32200 TCP BBN7ACRS ; Daemon IP port
32201 TCP BBN7ACRS NODELAYACKS ; Daemon SSL port
32202 TCP BBNS001 ; SOAP JMX Connector port
32203 TCP BBNS001 ; ORB port
32204 TCP BBNS001 NODELAYACKS ; ORB SSL port
32205 TCP BBNS001 ; Administrative console port
32206 TCP BBNS001 NODELAYACKS ; Administrative console secure port
32207 TCP BBNS001 ; HTTP transport port
32208 TCP BBNS001 NODELAYACKS ; HTTPS transport port
32209 TCP BBNS001 ; Administrative Local Port
32210 TCP BBNS001 ; High availability manager comm port
32211 TCP BBNS001 ; Service Integration port
32212 TCP BBNS001 NODELAYACKS ; Service Integration secure port
32213 TCP BBNS001S ; Service Integration MQ interoper
32214 TCP BBNS001S NODELAYACKS ; Service Integration MQ inter secure
32215 TCP BBNS001 ; Session Initiation Protocol (SIP)
32216 TCP BBNS001 NODELAYACKS ; Session Init Protocol (SIP) secure
8879 TCP BBODMGR ; SOAP JMX Connector port
7277 TCP BBODMGR ; Cell Discovery port
9809 TCP BBODMGR ; ORB port
9090 TCP BBODMGR ; HTTP port
9043 TCP BBODMGR ; HTTPS port
5755 TCP BBODMNC ; Daemon port
5756 TCP BBODMNC ; Daemon SSL port

; WAS Base Node entries

8880 TCP BBOS001 ; SOAP JMX Connector port
;2809 TCP BBOS001 ; ORB port (COMMENT THIS ONE OUT)
9080 TCP BBOS001 ; HTTP port
9443 TCP BBOS001 ; HTTPS port
5655 TCP BBODMNB ; Daemon port
5656 TCP BBODMNB ; Daemon SSL port
; WAS ND Node entries
8879 TCP BBODMGR ; SOAP JMX Connector port
7277 TCP BBODMGR ; Cell Discovery port
9809 TCP BBODMGR ; ORB port
9090 TCP BBODMGR ; HTTP port
9043 TCP BBODMGR ; HTTPS port
5755 TCP BBODMNC ; Daemon port
5756 TCP BBODMNC ; Daemon SSL port
; WAS Federation entries
8878 TCP BBON001 ; SOAP JMX Connector port
7272 TCP BBON001 ; Node Discovery port
2809 TCP BBON001 ; Node Agent’s ORB port
9810 TCP BBOS001 ; Base Server’s ORB port

SACONFIG DISABLED

Appendix A. z/OS 1.12 AD-CD example 65

 DEVICE PORTA MPCIPA
LINK ETH1 IPAQENET PORTA
HOME 10.1.1.2 ETH1

DEVICE PORTB MPCIPA

LINK ETH2 IPAQENET PORTB
HOME 192.168.0.61 ETH2

BEGINRoutes
; Destination SubnetMask FirstHop LinkName Size
ROUTE 192.168.0.0 255.255.255.0 = ETH2 MTU 1492
ROUTE 10.0.0.0 255.0.0.0 = ETH1 MTU 1492
ROUTE DEFAULT 192.168.0.1 ETH2 MTU 1492
ENDRoutes

ITRACE OFF

IPCONFIG NODATAGRAMFWD

UDPCONFIG RESTRICTLOWPORTS

TCPCONFIG RESTRICTLOWPORTS

START PORTA
START PORTB

66 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
Related publications

The publications listed in this section are considered particularly suitable for a more detailed
discussion of the topics covered in this book.

IBM Redbooks
For information about ordering these publications, see “How to get Redbooks” on page 67.
Note that some of the documents referenced here may be available in softcopy only.
򐂰 IBM System z Personal Development Tool Volume 1 Introduction and Reference,
SG24-7721
򐂰 IBM System z Personal Development Tool Volume 3 Additional Topics, SG24-7723
򐂰 IBM System z Personal Development Tool Volume 4 Coupling and Parallel Sysplex,
SG24-7859
򐂰 Communications Server for z/OS V1R9 TCP/IP Implementation Volume 1: Base
Functions, Connectivity, and Routing, SG24-7532

Other publications
These publications are also relevant as further information sources:
򐂰 z/Architecture Principles of Operation, SA22-7832
򐂰 System z Personal Development Tool User’s Guide and Reference, G229-1101

How to get Redbooks

You can search for, view, or download Redbooks, Redpapers, Technotes, draft publications
and Additional materials, as well as order hardcopy Redbooks, at this Web site:
ibm.com/redbooks

Help from IBM

IBM Support and downloads
ibm.com/support

IBM Global Services

ibm.com/services

© Copyright IBM Corp. 2009, 2011. All rights reserved. 67

68 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
Index
CHPID number 30
Symbols command
.bashrc, changes 12 adstop 51
/etc/profile 12 alcckd 48
/etc/profile.local 12 awsckmap 48
/etc/sysctl.conf 11 awsin 50
/home file system 3 awsmount 49
/usr/z1090/bin 9 awsstart 48
awsstat 49
Numerics awsstop 23
1090 hardware key activation 14 cpu 51
1091 token 58 d 51
11S and MTSN fields 15 find_io 62
3270 interfaces 28 interrupt 51
3270 nulls 59 ipcs 8
3270 sessions, starting 22 ipl 23
3270port parameter 28 ipl_dvd 50
32-bit support 4 istep 51
3390 volumes, additional 24 memld 51
4-mm tape drive 55 mt 59
oprmsg 50
query 51
A ready 50
activation, token 15 restart 51
AD system, device addresses 20 st 51
AD system, installation 19 start 51
Adapter Interrupt Facility 56 stop 51
adstop command 51 storestatus 51
alcckd command 48 storestop 51
aliasing, IP 57 sys_reset 51
APAR VM64385 58 sysctl 8
Application Development System 19 ulimit 8
ath0 device 44 z1090instcheck 59
aws3274 device manager 28 z1090ver 48
awsckd, number units 60 commands, package 47
awsckmap command 48 core image files 3
awsin command 50 cpu command 51
awsmount command 49 CRYPTO instructions 60
awsOSA performance 43
AWSPRT, translation table 58
awsstart 22 D
awsstart command 48, 58 d command 51
awsstat command 49 db_recovery, rpm error 58
awsstop command 23, 48 device addresses, for AD 20
awstape, format 18 DEVICE name 30
devmap 52
devmap, for AD 21
B disk partitions, deleting 59
beagle 56 disk planning 3
beagle application 4 disk usage layout 4
BIOS level 60 dmidecode rpm 4
bonding, LAN 28 dual boot system 4

C E
CD/DVD drive access 9 Ethernet adapters, multiple 58

© Copyright IBM Corp. 2009, 2011. All rights reserved. 69

Ethernet ports, PCMCIA 57 LINK parameter 30
ethtool usage 43 Linux installation 4
external interrupt 51 Linux releases, new 58

F M
find_io command 29, 44, 48, 62 man files, installation 10
firewall functions 5 media, software 18
firewall, Linux 42 memld command 51–52
floating point hardware 55 MIH value, OSA 30
MIH values 25
MIPS 55
G MONITOR, z/VM 58
gnome, selection 4 msgmax and msgmnb settings 12
gunzip utility 20 mt command 59
GVRP, for OSA 58 MTU size 57
gzip, compression 18

N
H national language support 58
hardware key 58 net.core.rmem_max parameter 43
HCD utility 57 new release 16
HDD, changing 59 NFS server 56
hyperthreading 4 NFS server, usage 56
NOGVRP parameter 58
I non-QDIO mode 29
ibmsys1 userid 20, 58
ibmsys1, userid 9 O
IBMUSER password 23 OAT table 45
ICKDSF job 24 OAT, default 56
IECIOSxx member 25 OAT, filtering 56
ifconfig command 8 OMA format 60
installation, rpm problem 58 openSUSE 10.3 56
Installer options 10 operating systems, multiple 25
installer program 10 oprmsg command 50
interrupt command 51 ordering information 2
IP traffic, filtering 56 OSA devices 57
ipcs command 8 OSA interfaces 56
ipl command 23, 48 OSA performance 43
IPL operation 22 OSA QDIO, multiple 57
ipl_dvd command 50 OSA/SF 56
iptables 35, 40 OSA/SF utility function 45
iso fonts 8 OSA-Express 28
istep command 51 OSA-Express emulation 57
OSA-Express interface, filtering 56
J OSA-Express2 offload functions 57
jumbo frames 57 OSN operation 57

K P
k3b package 4 packet size, TCP/IP 57
kernel mode 59 password, IBMUSER 23
kernel.shmmax 60 PATH 9
KVM 1 PC Card 57
PCMCIA card, Ethernet 57
PCOM 60
L PCOM, 3270 emulator 6
LAN setup 42 PING command 46
LCS mode 29 pmtools rpm 4
LD_LIBRARY_PATH 9 PORTNAME (in the TRLE) 30
lease extension, token 15 PowerTerm 6

70 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
printer output 59 sys_reset command 51
PROFILE, z/OS TCP/IP 64 sysctl command 8
PSW values 52 systcl parameter 43
SYSTCPT DD statement 46
System z software 17
Q
QDIO interface, multiple 57
QDIO mode 28 T
QDIO operation, advantages 45 tap (tunnel) interfaces 56
QDIO setup 29 TCP/IP stacks, multiple 56
query command 51 TCP/IP, starting z/OS 60
telnet session 44
telnet-server, selection 4
R thin interrupts 56
RDzUT 58 TN3270E clients 6
ready command 50 TN3270e clients 6
Redbooks Web site 67 TN3270e connections 28
Contact us viii token 48
releases, new 16 token serial number 13
resolver, z/OS 40 TRACERTE command 46
Resource Link 16 TRL entry 30
Resource Link, activation 14 TRL major node 64
restart command 51 TSO commands, NETSTAT 46
RMF 60 tunnel connection 30
root partition 3 tunnel connection, usage 44
root userid 59
router personal 42
U
UIMD (for Unique Identifier) 13
S UIMD service 10
Scenario 2 33 ulimit command 8, 12
Scenario 3 35 ulimit commands 12
Scenario 4 37 unit address, OSA 56
Scenario 5 39 Universal Time 4
SCSI DLT tape drive 55 Unsupported Function, 3270 23
SCSI tape 59 upddecode tool 4
search paths 50 USB3 port 55
Secure Update Utility 15
SecureUpdateUtility program 14
SEL protection 42 V
SELinux 6 VIPA functions 57
serial numbers, 1090 13 VLAN, usage 58
service uimd commands 13 VLAN/VSWITCH in z/VM 58
shk-server 10 VMAC support 46
shmall value 11 VMWare 1
shmmax value 11 vsftp, selection 4
shutdown, z/OS and 1090 23 vswitch support 46
SIOCGIFINDEX failed 56 VTAM commands 46
SNA 29 VTAMLST ATCCON00 30
SNA 3270 28
SNA operation 28, 45
sntl-sud 10 W
software media 18 WebSphere Application Server 21
st command 51 wireless connection 30
start command 51 wireless usage 44
START name 30
stop command 51 X
storestatus command 51 X Software Development package 5
storestop command 51 x3270 fonts 8
SUSE components, adding 59 x3270 installation 6
swap partition 3 x3270, obtaining 6

Index 71
x3270, startup 22
x3270, to z/OS TCP/IP 44
Xen 1

Z
z/OS 18
z/OS TCP/IP 28–29
z/VM 18
z/VM installation 19
z/VSE 18
z/VSE installation 19
z1090 rpm 10
z1090instcheck command 13, 48, 59
z1090ver command 48
zIIP or zAAP, performance 55

72 IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
IBM System z Personal
Development Tool: Volume 2
Installation and Basic Use
IBM System z Personal Development
Tool: Volume 2 Installation and Basic
IBM System z Personal Development Tool: Volume 2 Installation and
IBM System z Personal Development Tool: Volume 2 Installation and Basic Use
(0.2”spine)
0.17”<->0.473”
90<->249 pages
IBM System z Personal
Development Tool: Volume 2
Installation and Basic Use
IBM System z Personal
Development Tool: Volume 2
Installation and Basic Use
 Back cover ®

IBM System z
Personal Development Tool
Volume 2 Installation and Basic Use ®

System z This IBM Redbooks publication introduces the IBM System z

Personal Development Tool (zPDT), which runs on an underlying
INTERNATIONAL
Development Tool
Linux system based on an Intel processor. zPDT provides a TECHNICAL
System z system on a PC capable of running current System z SUPPORT
Full z/OS usage
operating systems, including emulation of selected System z I/O ORGANIZATION
Linux base devices and control units. It is intended as a development,
demonstration, and learning platform and is not designed as a
production system.
BUILDING TECHNICAL
This book, providing specific installation instructions, is the INFORMATION BASED ON
second of three volumes. The first volume describes the general PRACTICAL EXPERIENCE
concepts of zPDT and a syntax reference for zPDT commands
and device managers. The third volume discusses more IBM Redbooks are developed
advanced topics that may not interest all zPDT users. The IBM by the IBM International
order numbers for the three volumes are SG24-7721, Technical Support
SG24-7722, and SG24-7723. Organization. Experts from
IBM, Customers and Partners
from around the world create
The systems discussed in these volumes are complex, with timely technical information
elements of Linux (for the underlying PC machine), z/Architecture based on realistic scenarios.
(for the core zPDT elements), System z I/O functions (for Specific recommendations
emulated I/O devices), and z/OS (providing the System z are provided to help you
implement IT solutions more
application interface), and possibly with other System z operating effectively in your
systems. We assume the reader is familiar with the general environment.
concepts and terminology of System z hardware and software
elements and with basic PC Linux characteristics.

For more information:

ibm.com/redbooks

SG24-7722-03 ISBN0738435775