What you should know about z/OS, z/VSE, z/VM and their supported products for the IBM Z Personal Development Tool (zPDT)

IBM Software stacks for zPDT systems provide qualified PartnerWorld Independent Software Vendors (ISVs) with z/OS, z/VM, z/VSE and associated middleware products. The z/OS Software stack for the zPDT systems is built two times per year typically coinciding with the release of new versions of z/OS. The z/VM and z/VSE Software stacks are updated periodically.

NOTE: All IBM Software stacks for zPDT systems are provided via downloads from the site. DVDs are not available.

NOTE: There is an annual US $900 subscription fee for the use of the IBM Software stacks for zPDT systems. This annual fee covers the z/OS, z/VM, and z/VSE Software stacks in any combination. One stack, two stacks or three stacks are available for a single US $900 fee.

IMPORTANT:     Please READ the Disclaimer!!

Announcements, Changes and Updates for zPDT Systems


IMPORTANT Zowe information when running on a zPDT system

Important Information about ZOWE use on ADCD The product has been configured for Internal use. Meaning the IP addres is 10.1.1.2 . So all a user needs to do is import the certificate from the Unix System Services directory described in the steps further down on this page. This will allow the user to start ZOWE witout creating a new Instance. The section below describes the issue's we found during ZOWE testing:

Known Issues:

  1. ZOWE failed to connect when running under z/PDT. The following value has to be added to the instance.env file in the directory below:
    ZWED_node_cluster_storageTimeout=30000
    /apps/zowe/v10/server/zwe1sv/

    Edit the file and add the above line to the instance.env example partial instance.env file.

    ROOT_DIR=/usr/lpp/zowe/
    ZOWE_PREFIX=ZWE
    ZOWE_INSTANCE=1

    ZWED_node_cluster_storageTimeout=30000

  2. When a new Instance is created the KEYSTORE_DIRECTORY=value in the instance.env file points to /global/ this is the default so it needs to change to correct location of the keystore: /apps/zowe/v10/security/keystore
  3. The VT Terminal SSH on the ZOWE Desktop fails to connect. This is a known issue and a workaround has been provided. The workaround is to use TELNET using port 1023, this provides access to Unix System Services on the system. We set the default in VT Terminal Desktop. Important note: If you delete and recreate the Instance the VT Terminal Desktop will revert back to the orignal definition and you will need to make the change below again.
    Go into ISH or OMVS and go to the directory:
    /apps/zowe/v10/server/zwe1sv/workspace/app-server/ZLUX/pluginStorage/ org.zowe.terminal.vt/sessions/
    Edit the file below and change port and type as shown:
         _defaultVT.json
         {
           "host": "",
           "port": "1023",
           "security": {
             "type": "telnet"
           }
         }
         
  4. Steps necesary to create a new instance on ADCD: See the data set named ZWE100.SVSC.CONFIG on the ADCD. Look at the #READNOW member. It will contain information to create a new Instance and Keystore. There will be four members, twofor creating the Internal Instance and two for creating an External Instance. Additionally information about values that need to be placed in the NEW instance.env can be found in the #READNOW member.

Db2 12 now supports encryption of Db2 data with z/OS DFSMS data set encryption, and function level 506 introduces new policy controls for managing of key labels. For more information go to URL: DB2 Administration Tool(DM) and DB2 V12 with V12R1M506

The option to use Secure SSL/TLS for TN3270 has been provided with this ADCD release. We have defined a Self-Signed certificate for temporary use until you receive your own certificate from a VALID security authority. It currently is working on this ADCD release.
As a result, and if you are using PCOMM, you will need to modify your configuration to allow PCOMM to use SSL/TLS.
The only reason you need to do this is if you are using PCOMM and this Self-Signed Certificate. We suspect the newer versions of PCOMM, after V6.0, will not require this process and most third party emulators will work without this process. We believe the most current version of PCOMM is V13 and it will only run on Windows 10 and above. If you still have the Windows 10 box you should try it out. If you are using a third party TN3270 emulator then you should check with owner of the third party TN3270 emulator for assistance with implementing a Self-Signed Certificate to the emulator.
Of course, if you receive your own certificate then you will simply need to update the Policy Agent TLS control file with the new ring and possibly certificate name.
The following is the information you will need to use and re-configure the Policy Agent for whatever reason you desire.

  • ADCD.Z24B.SSL.PAGENT.SIGNER00.ARM is to be downloaded to your workstation in ASCII mode. If you are using PCOMM then you need to use the PCOMM certificate management utility and add it to your key database as a Signer Certificate.
  • Configure a NEW PCOMM session using the Secure Port, it is port 2023
    • Here is the example PCOMM security settings. Click on the Security Setup tab at the top of the session configuration.
    • Click the "Enable Security" box.
    • Click the "Telnet-negotiated" box if not already checked.
    • If you are NOT using the supplied self-signed certificate and your certificate is from an Authorized Certificate Authority, then CLICK the 'MicroSoft CrytoAPI (MSCAPI)".
      Otherwise if you are using the supplied self-signed certificate CLICK "IBM Global Security Kit (GSKIT)"
    • In the Security Protocol square: Select "TLS1.2" from the drop down menu.
    • You should be good to go...

USER.** libaries changed to use the ADCD release level &SYSVER, USER.Z24B, to provide uniqueness based on ADCD release level.

Console member in PARMLIB updated to allow Health Checker messages to roll off.

Downloads of ADCD z/OS V2R4 May Edition of 2020 images were made available via this website in conjunction with zPDT Version 1.8. All zPDT 1090 Software updates can be obtained for ALL zPDT Customers through Information Technology Company (ITC). Visit www.itconline.com and click on the zPDT Software Updates icon. IBM employees must obtain the zPDT 1090 SW updates from IBM Resource Link.

REMINDER: In order to install the new encrypted z/OS V2.4 ADCD, users must install as a prerequisite zPDT Version 1.8.


Currently supported IBM Software stacks for the zPDT and Download Information.

zPDT Redbooks

IBM zPDT Guide and Reference
PDF (3689KB)

zPDT 2016 Sysplex Extensions
PDF (2457KB)

Installing Linux for z Systems on zPDT
PDF (1655KB)


DISCLAIMER

The use of the z/OS, z/VM, and z/VSE IBM Software stacks (also known as ADCD) for zPDT systems are restricted to qualified PartnerWorld Independent Software Vendors (ISVs) who are active participants in the IBM Z Developer Discount Program (zDD) and are licensed to use the z Personal Development Tool (zPDT) system.

The IBM Software stacks and associated downloads are licensed to the specific system by zPDT machine type/model serial number and cannot be transferred to any other machine. The Programs provided in the IBM Software stacks and associated downloads, are owned by IBM or an IBM supplier, and are copyrighted and licensed, not sold. Use of the products provided in the IBM Software stacks and associated downloads, are subject to the terms and conditions of the IBM Customer Agreement (ICA) - Attachment for Developer Discount - z System, and associated Addendum, the individual product licenses, and the associated Application Developers Controlled Distribution (ADCD) License Agreements for each IBM Software stack (z/OS, z/VM, z/VSE).

Use of the software included with the IBM Software stacks on any other system or software emulator is strictly prohibited and is in violation of the terms and conditions of the ADCD License agreements and the z System Developer Discount offering.

If you have any feedback or questions, please respond to: ztech@us.ibm.com