GuangXingLiu

一蓑一笠一孤舟,一丈丝纶一鱼钩,一曲高歌一樽酒,一人独钓一江秋.

2021年10月20日

ADCD z/OS V2R4 May Edition of 2021

What you should know about ADCD.

The ADCD is built on a twice per year schedule typically coinciding   with the release of new versions of z/OS. The ADCD is created to   provide qualified Independent Software Vendors (ISVs) with the   latest z/OS System along with associated middleware products at the   latest available maintenance level.   The z/OS ADCD can run under the IBM's               z System Personal Development Tool (zPDT).          

NOTE:    There is an annual US $900 subscription fee for the use of the ADCD    Software distributions. This annual fee covers the z/OS, z/VM,    and z/VSE and Parallel System Starter System Software stacks and    is regardless if one, two, or all four ADCD stacks are requested.

Important:     Important information is found in this disclaimer so             Please READ the Disclaimer!!          

Announcements, Changes and Updates for this release.

 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 know the newer versions of PCOMM, after V6.0,  will not require any special action to use SSl/TLS and most third  party emulators will work as well. 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 SSl/TLS.

USER.** libaries changed to use the ADCD release level &SYSVER,   USER.Z24D,   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 2021     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.  

Table of Contents

How to request the ADCD z/OS V2R4 May Edition of 2021


  • If you are an existing ADCD subscriber, please send an email to          zTech@us.ibm.com         for re-validation and password reset.

  • Make sure that you are currently up to date on your z System     Developer Discount annual contracts and ADCD license agreements.

  • Please send an e-mail to          s390net@us.ibm.com         with "ADCD 2.4 May 2021 Request"     in the subject line. Please provide the following     information so we can process your request.

  •     Required information for Electronic download.    

    1. Company name

    2. zPDT Serial number

  • Once your request is verified and approved, we will provide you     with access to the download and notify you how to proceed.

  • For any questions about the download, write an email to          zTech@us.ibm.com    

  • For any technical issues or questions, post a new message in the     Discussion tab of the IBM Z Dallas ISV Center Community site at URL:          http://ibm.biz/DallasISVCommunity    

  • IBM employees wishing to acquire the ADCD please request by sending     a note to          zTech@us.ibm.com    

License

The ADCD is a customized bundle of z/OS and related products. It is  not an IBM program product and is not supported as a product. The  intent of the ADCD is to allow a user a way to quickly implement a  z/OS system in order to concentrate on application development. In  general choice of parameters and customizations are default install  options with some changes due to user experiences.

Approved ISVs with zPDT based systems will need to have agreed to the  ADCD license agreement, and have a signed System z Developer Discount  contract on file with IBM prior to receiving a copy of the z/OS ADCD.  All license and agreements are done through the System z Developer  Discount offering.

System Requirements

The currently supported ADCD environments is:

  • z/OS V2R4 May Edition of 2021 under zPDT

For information on the zPDT Version 1.6 release, please see        zPDT What is New      

For the z/OS ADCD and z/VM ADCD Startup        zPDT mimimum system requirements.      

The z/OS ADCD packet is in Linux gzip format.   The *.gz files are gzipped directly from the 3390   images running under zPDT.

Downloads

The ordering process to obtain z/OS, CICS, DB2, IMS, WAS and Tivoli   Omegamon in gzip zpdt formats, as well as their middlware versions,   is found at        Subsystem Downloads - Information    

Once you have ordered ADCD and received the authenication package,         Proceed to the ADCD Download Authentication page      

Customization Help and Location of Product PGMDIR's

A great deal of effort has gone into the ADCD to customize the   products. However, you may find some products that are not fully   customized or are customized with options that you need to change.   Included in this release, are files in the format of p.SVSC.l where   p=product HLQ and l=library name. The purpose of these files is to   provide PGMDIR's, README, and INSTALL instructions. This ADCD is   built from a driver system that uses different volume and library   names. Thus, you will notice that the names referenced in the SVSC   files are different than the ADCD. You may need to make translations   on names to implement in the ADCD. Included on the RES1   volume are datasets with HLQ of MVS.ZOSRxx that document MVS. The MVS   PGMDIR is contained in this grouping.



What's New in ADCD z/OS V2R4 May Edition of 2021

NOTE: As of ADCD z/OS V2R4 May Edition of 2021, distribution via   DVDs has been discontinued and all future distribution of ADCD   Editions will only be available via download.

The      ADCD Release Guide z/OS V2R4 May Edition of 2021,      also available on the download site, contains more information    about this edition. It also provides some additional notes and    tips to effectively manage the ADCD system.

the following Workflow Provisions have been added to the    Market Place:

  • Db2 v12 Full Instance

  • IMS v14 Full Instance

The following products have been added:

  • IBM Z Monitoring Suite V1.2.0

  • IBM Open Enterprise SDK for GO 1.1.6

  • IBM Application Discovery Connect for Mainframe v6.0.0

  • IBM z/OS Transparent Data Migration Facility v5.9.0

  • IBM Urbancode Deploy for z/OS v7.1.1

  • IBM Open Enterprise SDK for Python 3.9.0

  • IBM Engineering Workflow Management v7.0.1

  • IBM z Development and Test Environment Enterprise v13.0.0

  • IBM XML Toolkit for z/OS v1.11.0

  • IBM Data Virtualization Manager 1.1.0

  • IBM MQ for z/OS CD V9.2.2

The following products have been updated to PUT2103 / RSU2103

  • z/OS 2.4 and all incorporated products that provided maintenance      at the above stated level.

All of z/OS base, z/OS products and middleware volume size       has been increased to mod-9 (10,017 cylinders) to provide more       free space for expansion



Products contained in this release














Reported Problems, Fixes, Maintenance and Observations


  • zCX License Expiring awaiting fix see ADCD Download Update/Fixes     on the ADCD Download Authentication page for additional information

  • Issue installing 1090 z/PDT 1.7 GA Level -     Install fails for the GA 1.7 level on a system running RH6.x.     Please go to the          z/PDT forum         for additional information on the resolution.


Build Structure



Table_Product: - Volumes for Supported Products
Volume Description
D4DIS1,
     D4DIS2,
     D4DIS3 		These volumes contains the base MVS system software distribution      libraries. They contain the DLIB (Distribution Library) and zone      CSI's. These volumes are needed to install service or products on      the MVS system using SMP/E. These volumes are all 3390-9.
D4DBB1,
     D4DBB2,
     D4DBAR

D4DBB1 is a 3390-9 volume that contains       DB2 V11 related data. D4DBB1       contains the DB2 usercatlog,       USERCAT.Z24D.DB2VB.       Also D4DBB1 contains all DB2 target       libraries and DB2 V11 utility products.       This volume is not required to IPL but is required to bring up       DB2 V11.

D4DBB2 is a 3390-9 volume that contains       DB2 catalog and directories with HLQ DSNCB10, which are SMS       managed.       The volume is not required for IPL but is needed to bring up       DB2.

D4DBAR is a 3390-9 volume defined in a       new esoteric called DBARCH. This esoteric has been defined in       DB2, for allocating the archive logs into this storage volume.       This volume is required, if you want to bring up DB2 V11.

D4DBC1,
     D4DBC2,
     D4DBAR

D4DBC1 is a 3390-9 volume that contains       DB2 V12 related data. D4DBC1 contains       the DB2 usercatlog, USERCAT.Z24D.DB2VC.       Also D4DBC1 contains all DB2 target       libraries and DB2 V12 utility products.       This volume is not required to IPL but is required to bring up       DB2 V12.

D4DBC2 is a 3390-9 volume that contains       DB2 catalog and directories with HLQ DSNCC10, which are SMS       managed.       The volume is not required for IPL but is needed to bring up DB2.

D4DBAR is a 3390-9 volume defined in a       new esoteric called DBARCH. This esoteric has been defined in       DB2, for allocating the archive logs into this storage volume.       This volume is required, if you want to bring up DB2 V12.

D4C560  
   

D4C560 is a 3390-9 volume that contains       CICS 5.6 Target, DLIB and all related data for CICS 5.6.       USERCAT.Z24D.CICS560 resides on this       volume. This volume is not required to IPL but is required to       bring up CICS 5.6 and apply CICS maintenance.

D4C551  
   

D4C551 is a 3390-9 volume that contains       CICS 5.5 Target, DLIB and all related data for CICS 5.5.       USERCAT.Z24D.CICS550 resides on this       volume. This volume is not required to IPL but is required to       bring up CICS 5.5 and apply CICS maintenance.

D4W901,      D4W902

D4W901 and       D4W902       are 3390-9 volumes that contains target and distribution       libraries for Websphere Application Services.

D4IMF1,
     D4IME1  
   

D4IMF1 is a 3390-9 volume that contains       IMS Target, DLIB and all related data for IMS 15.       USERCAT.Z24D.IMS15 resides on this volume.       This volume is not required to IPL but is required to bring up IMS       and perform maintenance on       IMS.

D4IME1 is a 3390-9 volume that contains       IMS Target, DLIB and all related data for IMS 14.       USERCAT.Z24D.IMS14 resides on this volume.       This volume is not required to IPL but is required to bring up IMS       and perform maintenance on       IMS.

D4KAN1

D4KAN1 is a 3390-9 volume that contains       Target and DLIB libraries for Tivoli OMEGAMON v5.4.1.

D4BLZ1

D4BLZ1 is a 3390-9 volume that contains       Target and DLIB libraries for IBM Engineering Workflow Management       7.0.0. This volume is not required to IPL but is required to       bring up RTC.

D4INM1

D4INM1 is a 3390-9 volume that contains       Target and DLIB libraries for Installation Manager 1.8.8.


Table_SMS: - Volumes for SMS Support
Volume Description
D4USR1 The data class DCEXTEAV is defined to allow larger than four      Gigabyte dataset allocation. With this data class and the      accompanying storage group and class, a dataset can be allocated      on the provided SMS managed volume      D4USR1.      The ACS routines are      defined so no filtering is needed. To allocate and SMS managed      dataset, specify the data class (DCEXTEAV) in the allocation JCL      and the dataset will be defined on the provided volume.      Below are      the names of theTable_SMSI: - SMS InformationItemDescriptionDCEXTEAVData ClassSGEXTEAVStorage GroupSCEXTEAVStorage classD4USR1Volume defined to SGEXTEAV (Storage Group)SYS1.SMS.CNTLLocation of the SMS routines
D4ZCX1 The data class CXDC is defined to allow larger than four      Gigabyte dataset allocation. With this data class and the      accompanying storage group and class, a dataset can be allocated      on the provided SMS managed volume      D4ZCX1.      The ACS routines are      defined so no filtering is needed. To allocate and SMS managed      dataset, specify the data class (CXDC) in the allocation JCL      and the dataset will be defined on the provided volume.      Below are      the names of theTable_SMSI: - SMS InformationItemDescriptionCXDCData ClassCXROOTSGStorage GroupCXROOTSCStorage classD4ZCX1Volume defined to CXROOTSG (Storage Group)SYS1.SMS.CNTLLocation of the SMS routines


Table_zOWE: - Volume for zOWE Support
Volume Description
D4ZWE1 D4ZWE1 is a 3390-9 volume     that contains ZOWE Target, and DLIB This volume is not required to     IPL but is required to bring up zOWE .

 

Migration Guidelines

The following guidelines will make it easier for you to replace   this level of system software with new levels built the same way.

Only IBM-supplied system software should reside on   D4xxxx volumes   except for D4SYS1.   D4CFG1 contains RACF, IPL, and catalog   datasets that are user dependent.

The ADCD does not contain a generalized migration utility or process.   Each user has unique requirements. It is recommended that you build   a migration plan based on your unique needs.  The ADCD does have   some assistance. The ADCD uses a system of concatenated libraries   (see below) The highest level of concatenation is   USER.Z24D.xxxxxx   The ADCD distributes these libraries empty. It is recommended that   the user place changes or overrides in these libraries. It is further   recommended that the   USER.Z24D.xxxxxx   libraries be backed up regularily.   When a new ADCD release is installed the   USER.Z24D.xxxxxx   libraries can   be copied from backups to the new   USER.Z24D.xxxxxx   libraries to provide   assistance in migration of programs and parameters.

The ADCD is distributed with a standard library   concatenation for the following:


  • LINKLST

  • PROCLIB (including TSO procedures)

  • CLIST

  • ISPPLIB (TSO panels)

  • LPALIB

  • PARMLIB

  • VTAMLST

  • VTAMLIB

  • VTAM source

The configured order of concatenation is user,   ADCD developers, and z/OS system   datasets.   For example, the LINKLST concatenation would be as   follows:


  • USER.Z24D.LINKLIB

  • ADCD.Z24D.LINKLIB

  • SYS1.LINKLIB

USER.Z24D.xxxxxx   libraries have all been built on   D4CFG1   which is the only volume that should contain user data.

USER.Z24D.xxxxxx   will not be changed by ADCD or System processes; thus,   user updates in USER.Z24D.xxxxxx   will be retained between release levels.   ADCD.Z24D.xxxxxx libraries are allocated on   D4SYS1 and are the libraries that are used   by ADCD developers. No RACF rules exist on these libraries; however,   changes to these libraries could destroy customization necessary to   bring up many products. SYS1.xxxxxxx libraries should NEVER be   updated by users or ADCD development.  System libraries should ONLY   be updated through SMP/E install, maintenance processes, or like   processes.

NOTE:   Changes to System libraries or ADCD pre-customization may corrupt   your system and prevent or delay IBM support activites.

The correct procedure for a user update to system data is to:


  • Copy the system data from SYS1.xxxxx or ADCD.xxxx to    USER.Z24D.xxxxxx

  • Edit, compile, or run user program against the    USER.Z24D.xxxxxx    item

  • Re-ipl, recycle system service, or re-logon to TSO

Removing a user update would be the reverse of the above procedure.


LOADPARMS Options

NOTE:   JES2 should be COLD started the FIRST time you bring up the   system.


Table Listing of available pre-configured distributed LOADPARMS.
LOADPARM Description
CS CLPA and Cold start of JES2. Base z/OS system functions i.e. no       CICS, DB2, IMS, WAS, etc.
WS CLPA and Warm start of JES2. Base z/OS system functions i.e. no       CICS, DB2, IMS, WAS, etc.
00 CLPA and Warm start of JES2. Base z/OS system functions i.e. no       CICS, DB2, IMS, WAS, etc.
CI CLPA and Warm start of JES2. Loads CICS 5.6 and 5.5 libraries.    up       Starts up CICS 5.6 and RDz.
DB CLPA and Warm start of JES2. Loads DB2 V12 and V11 libraries.       Starts up DB2 V12 and RDz.
IM CLPA and Warm start of JES2. Loads IMS 15 and 14 libraries.       up       Starts up IMS 15 and RDz.
IZ CLPA and Warm start of JES2. Starts up z/OSMF and RDz.
WA CLPA and Warm start of JES2. Loads WAS 9.0       libraries.Starts up RDz. WAS needs to be manually started.
AL CLPA and Warm start of JES2. Loads all middleware libraries.       Starts up CICS 5.5, DB2 V12, IMS 15, z/OSMF and RDz.
DC CLPA and Cold start of JES2. Loads CICS, DB2 libraries.       Starts up CICS 5.6, DB2 V12, UCD 7.1.1, RTC 7.0.1 and RDz.
DW CLPA and Warm start of JES2. Loads CICS, DB2 libraries.       Starts up CICS 5.6, DB2 V12, UCD 7.1.1, RTC 7.0.1 and RDz.


Console PF Key Settings


Action/Command PFKey
Display Devices PF1
Display 3270 Devices PF2
Clear Top of Screen PF3
Create a 10-line Display Area PF4
Display Address Space Information PF5
Display Outstanding Reply Requests and Error Messages PF6
Display PF Keys PF7
Scroll Display Area PF8
Display TSO Users PF9
Display Active Address Spaces PF10
Display Active Jobs PF11
Clear Bottom Screen PF12


USERIDS


Table of Pre-Defined USERIDS. The following TSO Userids and Passwords have already been set up on your system:
Userid Password
ADCDMST (RACF special authority) SYS1 or ADCDMST
IBMUSER (RACF special authority) SYS1 or IBMUSER
SYSADM (DB2 and RACF special authority) SYS1 or SYSADM
SYSOPR (DB2 and RACF special authority) SYS1 or SYSOPR
ADCDA - ADCDZ TEST
WEBADM WEBADM
OPEN1 thru OPEN3 SYS1


Maintenance Service Levels

All the products on the ADCD consist of maintenance that is in a   closed status. A PTF that is still in open status or has other than a   document hold at the time the ADCD was built would not be added to   the ADCD. The following PUT levels may be minus PTFs that were open   at build time. Also some functions may be better than the PUT level   due to the addition of RSUs and individual PTFs. In general the   following is valid.


  • All functions of the base z/OS V2R4 May Edition of 2021     are at PUT2103 / RSU2103

  • All functions of the CICS TS 5.6 are at PUT2103 / RSU2103.

  • All functions of the CICS TS 5.5 are at PUT2103 / RSU2103.

  • The functions of the DB2 11 base are at PUT2103 / RSU2103.

  • The functions of the DB2 12 base are at PUT2103 / RSU2103.

  • All functions of the IMS 14.1.0 are at PUT2103 / RSU2103.

  • All functions of the IMS 15.1.0 are at PUT2103 / RSU2103.

  • IBM Z Monitoring Suite V1.2.0 is at PUT2103 / RSU2103.


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.



作者:nova636 , 分类:Simulator , 浏览:859 , 评论:0

发表评论:

Powered By Z-BlogPHP 1.7.3