Specifications

6 IBM System z Personal Development Tool: Volume 3 Additional Topics
value shown is typical of a 64-bit Linux distribution. However, some distributions have this
number set much smaller and you may receive a warning message for this line.
򐂰 Line 4 (msgmni) is appropriate for a reasonable number of zPDT I/O devices. See 1.13,
“Devices, memory, msgmni, ulimit” on page 12 for more information.
򐂰 Lines 5 and 6 are needed for OSA operation. The exact values are not important but
should be larger than the default sizes in most distributions.
򐂰 Lines 7 and 8 reflect values recommended for heavy OSA usage, or larger frames.
򐂰 Lines 9, 10, and 11 reflect parameters for core image files. These are potentially important
if zPDT problems are encountered.
򐂰 Line 12 should be set as shown.
򐂰 Lines 11 and 12 are for the token modules and verify that the correct levels are present.
The levels distributed with zPDT should not be replaced with other versions, even if the
other versions have later levels.
򐂰 Line 13 verifies that 32-bit support is installed with Linux. This is needed by the token
modules.
򐂰 Line 16 reflects a module that might be useful for debugging. It is not critical.
򐂰 Lines 17 and 18 address applications that have caused zPDT problems in the past.
Additional checks may be added to later versions of z1090instcheck. Note that some checks
are absolute while others look for values in a range thought to be appropriate. Your output
from z1090instcheck may differ slightly from what is shown here as minor details may change
with zPDT updates or new Linux distributions.
1.6 CPs, processors, threads, and tokens
The L01 model of the 1090 provides one CP. The L03 model provides up to three CPs. 1091
tokens typically provide three CPs, but this is variable. Each can be used as a normal CP or
as a zIIP, zAAP, or IFL. The model number determines the maximum number of CPs or zIIPs
or zAAPs or IFLs for the token—and the model number is determined by the USB hardware
key (token). This discussion refers to CPs, but also applies to zIIPs, zAAPs, and IFLs. The
CPs of an L03 may be used in a single instance (that is, three CPs available to a single copy
of z/OS) or in three instances (each with a single CP) or some combination of these.
2
The
System z CPs (or zIIPs, or zAAPs, or IFLs) are the logical product of the 1090 system.
Tokens with one, two, or three licenses are considered standard zPDT tokens. Tokens with
more licenses may be available under special zPDT license arrangements (typically as part of
RDzUT or RD&T products). Operationally, a 1090/1091 license is a 1090/1091 license; it
makes no difference whether it originates from a single standard token, multiple standard
tokens, or a larger non-standard token, or whether it is from local tokens or a remote license
server.
A 1090 system (as available to qualified PartnerWorld® ISVs, IBM internal use, and other
users) may use multiple tokens, and have up to eight CPs (or a mix of speciality processors)
in one zPDT instance. A 1091 system (as used by RDzUT and RD&T) may use multiple
tokens and have more than three CPs (or mixes) in a zPDT instance only with additional
license features.
There is not a one-to-one correspondence between logical CPs and underlying processors
(cores) on the base hardware. Each zPDT CP is represented by a Linux process on the
2
Multiple instances are something like multiple LPARs, but without some of the auxiliary facilities of LPARs.