Linux and zPDT installation
The zPDT system operates as a normal Linux application. 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 zPDT usage. After you have gained some experience with zPDT, you can explore other installation and usage arrangements. Many of our choices are arbitrary and simply reflect our preference for a simple Linux.
We assume the PC is dedicated to Linux, with the zPDT application used when wanted. If this is not the case, you might consider alternatives:
•For a laptop, you might obtain a separate hard disk for Linux. Changing the hard disk drive in most laptop machines is quick and easy.
•You might consider a dual boot environment, to alternate between Microsoft Windows and Linux.
•If zPDT usage represents a substantial investment for you, consider purchasing a separate machine for it. The cost of a modest PC is often insignificant when measured against the overall investment in System z usage.
•Virtual environments are discussed in Chapter 15 of the third document in this series (SG24-7723-05 or later).
For some of our 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 might be different. The zPDT functions are not related to these controls, except that you might need to open firewall access for TCP/IP connections to the zPDT functions. A number of different LAN and TCP/IP configurations are explored in Chapter 3, “LANs and TCP/IP” on page 25.
Ordering requirements
This document does not provide detailed ordering information for zPDT. The ordering process might differ for various categories of users and for different countries. Whatever ordering process is used should result in the following:
•One of the zPDT-supported Linux distributions (specified versions of Red Hat Enterprise Linux (RHEL) or SUSE Linux Enterprise Server (SLES)). These and alternatives are discussed in Volume 1 of this documentation series. This base Linux is not supplied by IBM. It might need to be ordered, or it might be downloaded from a website.
•A zPDT token (which might need to be activated through an IBM business partner, zPDT supplier, or through IBM ResourceLink). (An alternative to individual tokens exists. This is discussed under “License & serial number servers” in the third volume of this documentation series.)
•The zPDT software, which must be installed before the token can be activated (if it is not supplied already activated). The base zPDT software does not include any System z operating systems.
•Whatever System z software you plan to use, in a format usable with zPDT. This might require a different ordering process than ordering zPDT itself.
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 zPDT from the supplier of that software.
Installation overview
A summary of the usual installation sequence is this:
1. Read this series of books. You might not remember all the details at this stage, but 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 zPDT, install a simple system first, before attempting something more complex. Do not use root for all installation and operation actions.
2. Think about your disk partitioning, especially if you plan to install major applications in addition to the zPDT package or if you have especially large PC memory.
3. Gather the required software packages:
– Linux for your base PC. zPDT checks for Red Hat or SUSE indicators and will not install with other Linux distributions.1
– The zPDT software (which might be obtained on a CD or DVD, or by a download).
Two zPDT packages are available, one for 1090 tokens and one for 1091 tokens. The proper package must be used with the proper token.
For each package, two prerequisite modules, the zPDT modules, and the license agreement are all in a single (non-rpm) file. The file contains both the Red Hat and SUSE versions of the zPDT code. The proper version is automatically installed on your system.
– Your System z software (z/OS, IBM z/VM®, or IBM z/VSE®) in a format usable with zPDT.
4. Follow the installation steps described later in this chapter:
a. Install Linux.
b. Install x3270 (or another 3270 emulator) if it is not included in your base Linux distribution. Optionally, customize the x3270 keyboard.
d. Install the zPDT package.
e. Customize two Linux files (sysctl.conf and .bashrc).
f. Copy or create a devmap.
5. Activate your zPDT token if necessary, as described in 1.5, “Token activation and renewal” on page 11. You cannot do this until the zPDT package is installed. (This step might have been done by a business partner or zPDT service provider.)
6. Generally following Chapter 2, “AD CD z/OS installation” on page 15, 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 zPDT 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 might 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 might require additional Linux drivers or upgrades. If you have a new PC model, or an unusual configuration, you must 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 zPDT 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 might need to be much larger. There should be sufficient free space to accept one or more large core image files.4
•A swap partition for Linux. We suggest 4 GB (or larger)
A common recommendation is (real memory size) + 2 GB, although this might 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.
This suggested 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 might 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 might 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. Consider the following requirements and suggestions:
•You must include Linux 32-bit support, which is an option during Linux installation. It is required for the zPDT token drivers. (On RHEL 6.x systems you need the libstdc++-xx-xx.i686.rpm, not the compat-libstdc rpm. On RHEL 6.0 the specific name is libstdc++-4.4.4-13.el6.i686, but this might be updated for later releases. In the Add/Remove Software function (during RHEL installation or later updates) there is a small box that shows up after clicking Filters on the menu bar, with the label Only Native Packages. This was checked by default. You should uncheck it to see the i686 rpms.)
•Select Universal Time (UTC) for your base PC, if this is possible. (This might 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, because this can disrupt your zPDT usage.)
•Although not a Linux option, machine hiperthreading (if available) must be disabled at the BIOS level. z/OS slowdowns might occur at random times if you have hiperthreading active when running zPDT with multiple CPs.
•For Red Hat releases we recommend including the dmidecode rpm. For SUSE releases we recommend including pmtools. Both packages include the upddecode tool. These packages 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 sometimes use gnome as our desktop manager, and this is reflected in our examples. With the advent of gnome 3, we sometimes use the Xfce desktop (which may be selected among the other desktop choices during Linux installation). The xfce interface is more like gnome 2. You could also select KDE (we have no indication that it would not work with zPDT). zPDT is not sensitive to the desktop manager.
•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 might 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 might be needed to find this path.
•Install vsftp or some other Linux ftp package. It is not needed for zPDT usage, although you might want to transfer files between Linux and z/OS using ftp.
•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 new hardware on your PC.
•You must manage whatever firewall and other security functions that you install with your Linux. We suggest initially disabling any firewall when first working with zPDT. After you are familiar with zPDT 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.
TN3270e clients
IBM has used these TN3270e clients with the recent zPDT offerings:
•x3270 (recent versions)
•Recent PCOMM releases (running on Windows systems)
We most commonly use x3270. Our last step during many Linux installations has been to install x3270, because it was not included with most current Linux distributions.5 An x3270 package is usually a single rpm, such as:
x3270-3.2.20-467.1.x86_64.rpm
Other x3270 levels may be used, or another 3270 emulator may be used.
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-side 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):6
# cd /usr/share/X11/app-defaults
This directory might 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 can consider using a local x3270 profile, which is 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()
:<Key>Return: Enter()
<-- delete this line
:<Key>Linefeed: Newline()
<-- delete this line
:<Key>Backspace: Erase()
<-- delete thisline
<Key>Control_R: Enter()
<-- add these lines
<Key>Control_L: Reset()
<Key>Return: Newline()
<Key>Pause: Clear()
<Key>BackSpace: BackSpace() Delete()
<Key>KP_Enter: Enter()
<---optional
<Key>End: EraseEOF()
<-- optional
<Key>Prior: PF(7)
<-- optional
<Key>Next: PF(8)
<-- optional
Shift<Key>Tab: BackTab()
...
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:
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()
<Key>Control_L: Reset()
<Key>Return: Newline()
<Key>Pause: Clear()
<Key>BackSpace: BackSpace() Delete()
It seems that x3270 keyboard files are sensitive to extra spaces and tab characters. Do not have anything after the
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 might not have its normal fonts. In the x3270 fonts menu there might 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
Always use the same Linux userid for zPDT operation. This Linux userid must be no longer than eight characters.7 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)
Other Linux distributions
The Linux distributions supported by zPDT are discussed in the first book in this series (IBM publication SG24-7721-05). zPDT is not designed to run on all Linux distributions. “Force fitting” zPDT to other distributions might 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 or /run/media/ibmsys1/xxxxx where xxxxx is the volume name or title of the CD/DVD. Whoever creates a CD/DVD can assign a title. You might 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/DVD.
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 zPDT, 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 place another directory containing a file named d earlier in the PATH, then the zPDT d function will not be available in the normal manner. Various internal zPDT functions assume they can access zPDT modules through PATH and LD_LIBRARY_PATH, so you must ensure that this is possible.
System time
We suggest setting your hardware clock to UTC time. This avoids problems when daylight saving time starts and stops. The zPDT token is sensitive to the hardware clock time8 and will not operate if the time appears to move backward. If the machine is shared with another operating system that expects local time (instead of UTC time), you might experience a one-hour non-operational time when shifting from daylight saving time to standard time.
1.3 Install zPDT software
Decide on the Linux userid you want 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 zPDT 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 zPDT instance will be used. (Multiple zPDT 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. By default, userid ibmsys1 has /home/ibmsys1 as its home directory and most zPDT 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)
# chown ibmsys1:zpdt /z (user ibmsys1 to own emulated volume directory)
A single executable file is used to install the zPDT software.12 The file name changes with maintenance releases, but has the following general format: 13
z1090-1-4.45.23.x86_64 (verify your exact file name)
z1091_xxx-1-4.45.23.x86_64 (it may be in this format)
The single file contains the following:
•An sntl-sud rpm at the correct level (A driver for the zPDT token)
•A zpdt-shk-server rpm at the correct level (Another token program)
•The primary z1090 or z1091 rpm for SUSE
•The primary z1090 or z1091 rpm for Red Hat
•An installer program that displays a license and then installs the rpms. The correct rpm (Red Hat or SUSE) is automatically selected for your base Linux system.
Proceed with zPDT installation as follows. The first goal is to move the installation file to a convenient directory, such as /tmp. If you obtained the zPDT installation file through ftp or another download method, you might have already placed it in /tmp.
(log on as ibmsys1)
$ su (change to root)
# cp /media/ROM/z1090-1-4-45.23.x86_64 /tmp (use the correct name)
# cd /tmp (the file is in /tmp)
Execute the installer program, for example:15
# chmod u+x z1090-1-4.45.23.x86_64 (make file executable, if not already)
Scroll through the license that is displayed and reply to the question at the end. The various rpms are then installed automatically. The zPDT installer program performs the following tasks, removing older versions of these programs as needed:
•Two prerequsite rpms are installed.
•The z1090 or z1091 rpm is installed, mostly in /usr/z1090/bin. (/usr/z1091/ is not used)
•A set of man files is loaded into /usr/z1090/man.
•A /usr/z1090/uim directory may be created.
Installer options
The installer program has three optional functions. Using the file name in the preceding example, the functions are listed here:
# ./z1090-1-4.45.23.x86_64 --refresh (reinstall current zPDT level)
# ./z1090-1-4.45.23.x86_64 --refreshall (reinstall zPDT and prerequsites)
# ./z1090-1-4.45.23.x86_64 --removeall (remove zPDT and prerequisites)
The prerequisites mentioned here are two rpms that are needed to access the USB token.
1.3.1 Alter Linux files
You must alter two Linux files before you can use zPDT. The first alteration is to /etc/sysctl.conf and involves changing a number of Linux kernel parameters. The second alteration is to the .bashrc file in your home directory; this adds the zPDT directories to your userid’s PATH variable.
You can manually edit the relevant Linux files or use zPDT commands to make the changes. The zPDT commands are listed here:
# /usr/z1090/bin/aws_config (You must be root to use this command)
$ /usr/z1090/bin/aws_bashrc (You must not be root to use this command)
The complete path name might be used for these commands (as shown here) because the Linux PATH might not yet include the zPDT files.
If you want to manually edit and add lines to /etc/sysctl.conf,17 we indicate the use of gedit but you may use any suitable editor (such as vi) to add the indicated lines.18 Unfortunately, some newer Linux versions restrict the gedit editor such that it is not usable when running as root. You might 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.
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.
# gedit /etc/sysctl.conf (the following lines should begin in column 1)
kernel.shmmax=18000000000 (17+ GB or more)
kernel.shmall=12000000 (12M pages or more)
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
net.core.rmem_default=1048576
# /sbin/sysctl -p /etc/sysctl.conf
Notes for sysctl values
The shmmax value shown establishes the maximum shared memory segment size that a user can request. All system z memory, plus several other zPDT work areas, are in Linux shared memory segments. The shmmax value should be 10-20% larger than the System z memory defined for the largest zPDT instance you use. The example shown (18000000000 bytes) would be suitable for a zPDT instance with up to 14-15 GB memory defined. There is no need to attempt an exact fit for the shmmax number; the example here may be used unless your define System z memory is larger than, for example, 15 GB.
Another parameter, kernel.shmall, sets the total shared memory size of all users. The value of shmall is specified in units of page size, which is usually 4096. The default value of shmall is usually quite large and acceptable.19 However, if you have multiple zPDT 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=12000000 (or larger, if appropriate)
This would result in the total amount of shared memory, for all users, to be 12,000,000*4096 or about 48 GB. This value should be greater than the number of zPDT instances times the System z memory size for each instance plus about 10-20%%. A number much larger than needed appears to do no harm.
Remember: the shmmax number is for bytes, and the shmall number is for pages.
The kernel.msgmni number, specified as 512 in this example, might 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 might 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.
Notes for .bashrc
The .bashrc file is changed, as follows:
# 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 these two Linux files. Errors here might 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.)
Other files
Check your zPDT distribution materials to see if there are sample devmap files that might be helpful.20 Copy these to /home/ibmsys1, for example:
$ cd /tmp/ROM (or wherever your zPDT source is)
$ cp aprof13 /home/ibmsys1/aprof13 (sample devmap)
$ chmod 664 /home/ibmsys1/aprof13
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.
Reboot Linux
Reboot Linux to pick up all the changes you have made. Then use the z1090instcheck command to partly verify your environment for running zPDT. Your new PATH is needed to find the command:
(log in as ibmsys1)
$ z1090instcheck (the same command is also used for 1091 systems)
If this command is not found, you do not have the PATH variables set or you did not install the zPDT code correctly. Note that this command does not check any devmaps that you may have defined or copied.
1.4 zPDT serial numbers
In the simple case, in which you have a single zPDT token that is used only on your PC, the System z serial number (when you start zPDT operation) is derived from the token serial number of the token.
In more complex environments, the System z serial number used may be set in other ways. This is described in detail in the chapter titled “License & serial number servers” in the third volume of this documentation series.
1.5 Token activation and renewal
|
Note: At the time of writing, the material in this section (about token license renewals) applies primarily to IBM internal users and a few special situations. It does not apply to tokens obtained through normal customer channels. It does not apply to 1091 tokens.
|
A USB hardware key (token) is normally valid for a year from the time it was last activated.21 Activation (and lease renewal) might 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.
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.
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 the following link 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.
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 zPDT system, using any USB port. (You must have already installed the zPDT software.)
2. Working as root, create a request file using the Secure Update Utility:
(log in with a normal zPDT userid, such as ibmsys1)
$ su (change to root)
# cd /usr/z1090/bin (must be in this directory)
# SecureUpdateUtility -r myrequest (myrequest is an arbitrary file name)
# exit (leave root)
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 email. (This typically takes about 10 minutes.) Receive this file and move it to your zPDT machine, if necessary. The file name will be the same name that you sent, but with .upw as the name extension.
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 zPDT operation.
1.6 Installing a new zPDT release
New zPDT releases are typically available through your Business Partner or (for IBM employees) 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.
2. Working as root, execute the distributed file. It will delete the previous release and install the new release. The process takes only a few seconds and does not disturb any of your customization.
1 The zPDT installation program checks the base Linux system for Red Hat or SUSE indicators. It is possible that other distributions might have one of these indicators, allowing zPDT installation to proceed.
2 This is not required. However, all our examples assume that the zPDT is operated through Linux userid ibmsys1. Whatever userid is used must be no longer than eight characters. Do not attempt to operate zPDT 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 might 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.
4 Core images (which are a debugging tool) should not be encountered often, but they might be needed for zPDT service in the rare event of serious problems with zPDT.
5 An exception is SLES 11, which includes x3270.
6 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 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.
7 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 This and the associated “time cheat” messages are discussed in the third volume of this series.
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 zPDT operation. Any userid with 8 or fewer characters can be substituted for ibmsys1, but that userid should be consistently used for all zPDT installation and operation actions.
11 This might not be the case for the IBM Open Client, but we ignore this exception here.
12 This file differs for 1090 and 1091 systems.
13 RDzUT users might have file names beginning with something like “z1091_801” instead of “z1090”. Use whatever file name is provided with your package.
14 This example assumes that ROM is the title of the CD. You must determine the title of your CD.
15 If you are coming from an older release of zPDT you might have multiple copies of sntl-sud or zpdt-shk-server installed and the installation step will fail. In this case, do the following:
# rpm -e z1090 (remove the old zPDT programs)
# rpm -e --allmatch sntl-sud (repeat for shk-server or zpdt-shk-server if necessary)
16 The “./” characters before the file name tell Linux to execute this file from the current directory.
17 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.
18 We suggest that you do not attempt to use vi unless you have a basic familiarity with it.
19 The default value on several distributions is 1,152,921,504,606,846,720, which is huge. However, on at least one IBM internally-used Linux the default is much lower and may need to be adjusted.
20 These might be provided by your zPDT service provider.
21 This was true at the time of writing. Future availability plans may manage this in a different way.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.