﻿Version GA11 z1090-1-11.57.10 Release Letter

1.  Product Description
The IBM System z Personal Development Tool (zPDT) provides System z functionality, with selected emulated I/O devices. The z1090 runs in a Linux environment.  As the name implies, a zPDT is intended for development and similar purposes such as education and demonstrations.  It lacks the Reliability and Service (RAS) and flexibility of a “real” System z machine and is not suitable for production use. This release letter refers to the zPDT that uses a token or USB hardware key defined as a Sentinel Hardware Key (SHK) for licensing management. Please reference the System zPDT Guide and Reference (SG24-8205-06) Redbook, section 1.3 Terminology changes for more information concerning licensing options.
2.   New Function
    • DEFLATE is active in this release!  
3.   Fixed in this release
    • Fixed an obscure convert Unicode instruction problem.
    • New ap_acptool command that works with the emulated cryptographic adapter and will eventually replace the current acptool command, introduced in base GA11 release.  See the command manpage for more information.
    • Token Licensing zip file validation prior to unzipping.

4.  System Configuration and Prerequisites
The supported levels of Linux must be at least the 64-bit version of the following: Red Hat Enterprise Linux (RHEL) 8.5 or greater, SLES 15 SP3 or greater, openSUSE Leap 15.3 or greater, and Ubuntu 20.04 or greater.  Earlier versions are not supported.

5.  Install z1090-1-11.57.10
If you are installing the 1090 application for the first time, refer to the Redbook titled IBM zPDT Guide and Reference System z Personal Development Tool (SG24-8205-05), chapter five, zPDT Installation.  Please be sure that you have installed the appropriate version of Linux and the prerequisites before proceeding to install the 1090 code.  If you have already installed the appropriate version of Linux and the required prerequisites, and you are upgrading from a previous zPDT level, please proceed to the next step.  

5.1. Install the 1090 application
You will use root to install the z1090 release.  As root, install z1090-1-11.57.10.x86_64 and accept the End User License agreement.  If you’ve downloaded the release, set the proper write and access permissions (either chmod 755 or u+x zPDT package name).

5.2. Execute z1090instcheck
The next step is to run the command z1090instcheck to check if conditions of your system are favorable for the 1090 application.  You should run this command from the user login configured to run the 1090 application.  If you choose to run from root, the path is /usr/z1090/bin/z1090instcheck. 

5.3. Plug the Sentinel Hardware Key (SHK)
If not already plugged in, be sure to plug the SHK into the appropriate USB slot.  If this is a brand new SHK that has not been activated yet, you’ll need the 1090 code to be able to activate the SHK.  The SHK may be plugged into any available USB 2.0 port.  If you are planning to install the SHK in a USB hub make sure that the hub is externally powered, otherwise, you could damage the SHK. 

6.  1090 Directory Structure
The following is the directory structure set up by the install process.  If the structure is not in place, the awsstart command will create it for you.  

/<homeDir>/z1090/logs		various traces are placed here	
/<homeDir>/z1090/configs	IOCDs, IOCP, activation profiles
/<homeDir>/z1090/disks		emulated disk volumes
/<homeDir>/z1090/tapes		emulated tape volumes
/<homeDir>/z1090/cards		input to emulated card reader
/<homeDir>/z1090/list		emulated printer output

(where /<homeDir> is whatever the home directory is for the given user)


7.  Known Restrictions, Exceptions, and Other Notes
7.1. Restrictions
    • SNA is not supported.
    • Multicast IP is not supported via OSE managed devices. Multicast IP is only supported with OSA defined in OSD mode.


7.2 Exceptions

    • None

7.3 Other Notes

    • awsrdr device statement without a full path specified will cause a core dump. Work around is to explicitly provide the full path statement. This is expected to allow the default to work in a future fixpack release.
