IBM Z Development and Test Environment notes
This publication is primarily about Independent Software Vendor (ISV) IBM Z Program Development Tool (IBM zPDT) (ISV zPDT) and is not intended to cover IBM Z Development and Test Environment (ZD&T) details. While much of the content might also apply to
IBM ZD&T, the text does not cover distinctions that are unique to IBM ZD&T. This appendix contains only a few details about IBM ZD&T. Any IBM ZD&T user (or potential user) should request access to documentation from their IBM ZD&T vendor.
The ISV zPDT package that is available to independent software vendors (ISVs) and IBM internal users requires a 1090 token (or a remote license manager with an equivalent license). It cannot function with a 1091 token. IBM ZD&T systems use 1091 tokens or a remote software license manager and cannot function with a 1090 token. Users of IBM ZD&T who require the Coupling Facility (CF) must purchase license features that enable that function.
The license terms and conditions for the two packages are different and not addressed in this publication. For complete licensing terms, contact your IBM representative, your IBM ZD&T supplier, or refer to the license documents that are supplied with your copy of IBM ZD&T.
Table D-1 summarizes some of the basic differences between ISV zPDT and IBM ZD&T.
Table D-1 1090 and 1091 comparisons
ISV zPDT usage: 1090 tokens
IBM ZD&T usage: 1091 tokens or equivalent
1090 token only. 1091 token is not usable (or equivalent remote licenses).
1091 token only. 1090 token is not usable (or equivalent remote licenses or a Gen2 software license).
Maximum of 8 CPs (with multiple tokens).
Maximum of 8 CPs (with multiple tokens or a “large” token or software license).
CF usage (under z/VM).
CF usage (under z/VM) only with an additional license feature.
1, 2, or 3 licenses in token. No way to order larger tokens.
Tokens with various numbers of licenses are available.
Installed rpm or deb name is z1090.
Installed rpm or deb name is z1091.
ISV zPDT and zD&T cannot be installed on the same machine.
“Standard” z/OS Application Development Controlled Distribution (ADCD) system.
Might have additions to the z/OS ADCD system, with possible delay for the most current z/OS.
Most zPDT commands are the same. A few have 1090 or 1091 versions.
Functional modules are installed in /usr/z1090/bin with additional materials in /usr/z1090/man and /usr/z1090/uim. zPDT instance files are in a subdirectory that is named z1090 in the Linux zPDT user ID home directory. There is no /usr/z1091 or ~/z1091 usage.
z/VM available (with proper license).
z/VM available for limited use only for use with the optional CF license.
IBM z/Transaction Processing Facility (z/TPF) not available at the time of writing.
z/TPF availability can be requested.
Installation and operational commands are as described in this publication. (Information Technology Company (ITC) offers additional interfaces with their uPDT package).
IBM ZD&T provides many additional installation and operation programs and interfaces that are not described in this publication.
The cpuopt statement in a device map (devmap) specifies optional parameters for the CPs. The following statement should be used only by IBM ZD&T customers who have the optional CF feature with their license:
cpuopt zVM_CouplingFacility (no blanks in operand)
cpuopt zVM_Coupling (This abbreviation can be used.)
The zVM_CouplingFacility operand is significant only for zD&T systems, which must have the proper license feature to enable it. In effect, the zVM_CouplingFacility function is always present for ISV zPDT systems.
 
Important: IBM ZD&T users must specify zVM_Coupling if their license has this feature. If the feature is present in the license and is not in the devmap, IBM ZD&T fails to acquire the licenses.
Tip: The CPU “model” number (which can be displayed on the MVS console or through some specialized IBM zSystems system instructions) is always 1090 regardless of whether ISV 1090 (token 1090) or some form of IBM ZD&T (token 1091 or software license) is used.
Here is another devmap statement:
[system]
...
rdtserver [email protected] # Rational License Server and port
The rdtserver statement is used only with an IBM ZD&T system. It points to an IBM Rational License Server that is used to supplement the IBM ZD&T license.1 A Rational License Server is not the same as an IBM ZD&T remote license server, and it is not required for basic
IBM ZD&T operation. The operand can be a normal URL domain name or an absolute IP numeric address. Also, note the format with the port number placed before the address. Multiple servers can be specified by using a colon as the separator:
The “software only” licenses that are available for IBM ZD&T are considered Gen2 licenses and have a number of different installation and update options. They are briefly described in Appendix C, “Generation 2 tokens and licenses” on page 379. The “software only” licenses are not available for ISV zPDT systems.
ISV zPDT (1090 tokens) and IBM ZD&T (1091 tokens) have different procedures for obtaining token licenses. Here are the differences For IBM ZD&T (1091 tokens):
•The license provider is aware of token license expiration dates (or a request is made to the license provider). No .req file is involved.
•The provider sends a compressed file that is installed with the Z1091_token_update command. Do not decompress the file.
•Especially for IBM ZD&T users with physical tokens, when you request a license file, ensure that you provide the correct token serial number. It is easy to misread the numbers on the token. With an incorrect token number, you received a license file and it appears to install on the token, but it does not work.
1 For more information about Rational licenses, contact your IBM marketing representative.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.145.27.58