Program Directory for IBM z Systems Development and Test Environment Tools

Program Directory for IBM z Systems Development and Test Environment Tools V11.0.2 Program Number 5725-G39 FMID HALMB02 For use with z/os v2.1 or higher Document date: December 2017 Notes: 1 IBM z Systems Development and Test Environment Tools

2 IBM z Systems Development and Test Environment Tools

Contents 1.0 Introduction.... 1 1.1 IBM z Systems Development and Test Environment Tools Description.. 1 1.2 IBM z Systems Development and Test Environment Tools FMIDs.. 1 2.0 Program Materials. 2 2.1 Basic Machine-Readable Material.. 2 2.2 Optional Machine-Readable Material. 2 2.3 Program Publications... 2 2.3.1 Basic Program Publications.. 2 2.3.2 Optional Program Publications. 2 2.4 Program Source Materials 3 2.5 Publications Useful During Installation... 3 3.0 Program Support... 4 3.1 Program Services...4 3.2 Preventive Service Planning. 4 3.3 Statement of Support Procedures 4 4.0 Program and Service Level Information. 5 4.1 Program Level Information.. 5 4.2 Service Level Information. 10 5.0 Installation Requirements and considerations. 6 5.1 Driving System Requirements. 6 5.1.1 Machine Requirements.. 11 5.1.2 Programming Requirements. 11 5.2 Target System Requirements...7 5.2.1 Machine Requirements.. 7 5.2.2 Programming Requirements. 7 5.2.3 DASD Storage Requirements.. 8 5.3 FMIDs Deleted.. 10 5.4 Special Considerations 10 6.0 Installation Instructions... 11 6.1 Installing zd&t Tools... 11 6.1.1 SMP/E Considerations. 11 3 IBM z Systems Development and Test Environment Tools

6.1.2 SMP/E Options Subentry Values 11 6.1.3 Upload SMPMCS and RELFILEs... 11 6.1.4 Sample Jobs.. 12 6.1.5 Perform SMP/E Allocation 13 6.1.6 Perform SMP/E RECEIVE... 13 6.1.7 Allocate SMP/E Target and Distribution Libraries... 13 6.1.8 Create SMP/E DDDEF entries 13 6.1.9 Perform SMP/e APPLY 13 6.1.10 Perform SMP/E ACCEPT.. 13 6.1.12 Authorize the program library 19 7.0 Notices.. 15 7.1 Trademarks 15 4 IBM z Systems Development and Test Environment Tools

Figures Figure 1: Publications Useful During Installation... 3 Figure 2 Component IDs... 4 Figure 3: Driving System Software Requirements... 7 Figure 4: Space Requirements.... 8 Figure 5: Storage Requirements for Target Libraries... 10 Figure 6: Storage Requirements for Distribution Libraries... 10 Figure 7: SMP/E Options Subentry Values... 16 Figure 8: Installation material... 17 Figure 9: Installation jobs provided... 17 5 IBM z Systems Development and Test Environment Tools

1.0 Introduction This program directory is intended for system programmers who are responsible for program installation and maintenance. It contains information about the material and procedures associated with the installation of IBM z Systems Development and Test Environment Tools. This publication refers to IBM z Systems Development and Test Environment Tools, as a part of the IBM z Systems Development and Test Environment V11.0.2. The Program Directory contains the following sections: 2.0 Program Materials on page 2 identifies the basic program material and documentation for IBM z Systems Development and Test Environment Tools. 3.0 program support on page 4 describes the IBM support that is available for IBM z Systems Development and Test Environment Tools. 4.0 Program and Service Level Information on page 5 lists the APARs (program level) and PTFs (service level) that have been incorporated into IBM z Systems Development and Test Environment. 5.0 Installation Requirements and Considerations on page 6 identifies the resources and considerations that are required for installing and using IBM z Systems Development and Test Environment Tools. 6.0 Installations Instructions on page 11 provides detailed installation instructions for IBM z Systems Development and Test Environment Tools. It also describes procedure for activating the functions of IBM z Systems Development and Test Environment Tools in the z/os source system. Before installing IBM z Systems Development and Test Environment Tools, read this Program Directory; then keep it for future reference. 1.1 IBM z Systems Development and Test Environment Tools Description IBM z Systems Development and Test Environment Tools is a part of IBM z System Development and Test Environment (zd&t), V11.0.2 and higher. The z/os component of the Tools participates in creating an image of an existing z/os system for porting to zd&t. For more information about zd&t, visit our web site at: https://www.ibm.com/support/knowledgecenter/sstqbd_11.0.0/com.ibm.zdt.nav.doc/topics/product_f amily_welcome.html 1.2 IBM z Systems Development and Test Environment Tools FMIDs IBM z Systems Development and Test Environment Tools consist of the following FMID: HALMB02 6 IBM z Systems Development and Test Environment Tools

2.0 Program Materials An IBM program is identified by a program number. The program number for IBM z Systems Development and Test Environment Tools is 5725-G39. Basic Machine-Readable Materials are materials that are supplied under the base license and are required for the use of the product. The program announcement material describes the features supported by IBM z System Development and Test Environment Tools. Ask your IBM representative for this information if you have not already received a copy. 2.1 Basic Machine-Readable Material The distribution medium for this program is downloadable files. This program is in SMP/E RELFILE format and is installed by using SMP/E. See 6.0, Installation Instructions on page 16 for more information about how to install the program. 2.2 Optional Machine-Readable Material No optional machine-readable materials are provided for IBM z Systems Development and Test Environment Tools. 2.3 Program Publications The following sections identify the basic and optional publications for IBM z Systems Development and Test Environment. 2.3.1 Basic Program Publications Information about the IBM z Systems Development and Test Environment is available at this location: https://www.ibm.com/support/knowledgecenter/sstqbd_11.0.0/com.ibm.zdt.nav.doc/topics/product_f amily_welcome.html 2.3.2 Optional Program Publications No optional publications are provided for IBM z Systems Development and Test Environment Tools. 7 IBM z Systems Development and Test Environment Tools

2.4 Program Source Materials No program source materials or viewable program listings are provided for IBM z System Development and Test Environment Tools. 2.5 Publications Useful During Installation You might want to use the publications listed in Figure 1 during the installation of IBM z Systems Development and Test Environment Tools. To order copies, contact your IBM representative or visit the IBM Publications Center at http://www-05.ibm.com/e-business/linkweb/publications/servlet/pbi.wss Figure 1: Publications Useful During Installation Publication Title IBM SMP/E for z/os User's Guide IBM SMP/E for z/os Commands IBM SMP/E for z/os Reference IBM SMP/E for z/os Messages, Codes, and Diagnosis IBM Online Library: Software Products DVD Collection z/os Information Roadmap Form Number SA22-7773 SA22-7771 SA22-7772 GA22-7770 SK3T-4271 SA22-7500 8 IBM z Systems Development and Test Environment Tools

3.0 Program Support This service number for IBM z Systems Development and Test Environment Tools is 0509531. 3.1 Program Services Contact your IBM representative for specific information about available program services. 3.2 Preventive Service Planning Before installing IBM z Systems Development and Test Environment Tools, make sure that you have reviewed the current Preventive Service Planning (PSP) information. Although SW, HW, and functional PSP Buckets might have overlap, review all that apply to this package to ensure that you identify all the known service that is required for your installation of this package. For program support, access the Software Support Website at http://www- 01.ibm.com/software/support/. For IBM z Systems Development and Test Environment support, access the Support Page at http://www-01.ibm.com/support/docview.wss?uid=swg27038434 3.3 Statement of Support Procedures Report any problem which you feel might be an error in the product materials to your IBM Support Center. You may be asked to gather and submit additional diagnostics to assist the IBM Support Center in problem analysis. Figure 2 identifies the component ID (COMPID) for zd&t Tools. Figure 2 Component IDs FMID COMPID Component Name HALMB02 5725G3923 IBM z Systems Development and Test Environment Tools RETAIN Release B02 9 IBM z Systems Development and Test Environment Tools

4.0 Program and Service Level Information This section identifies the program and relevant service levels of IBM z Systems and Development Test Environment Tools. The program level refers to the APAR fixes that have been incorporated into the program. The service level refers to the PTFs that have been incorporated into the program. 4.1 Program Level Information There is no program level information against previous releases. 4.2 Service Level Information No PTFs exist for this release of IBM z Systems Development and Test Environment Tools. 10 IBM z Systems Development and Test Environment Tools

5.0 Installation Requirements and considerations The following sections identify the system requirements for installing and activating IBM z Systems Development and Test Environment Tools. The following terminology is used: Driving system: the system on which SMP/E is executed to install the program. The program might have specific operating system or product level requirements for using processes, such as binder or assembly utilities during the installation. Target system: the system on which the program is configured and run. The program might have specific product level requirements, such as needing access to the library of another product for link-edits. These requirements, either mandatory or optional, might directly affect the element during the installation or in its basic or enhanced operation. In many cases, you can use a system as both a driving system and a target system. However, you can make a separate IPL-able clone of the running system to use as a target system. The clone must include copies of all system libraries that SMP/E updates, copies of the SMP/E CSI data sets that describe the system libraries, and your PARMLIB and PROCLIB. Use separate driving and target systems in the following situations: When you install a new level of a product that is already installed, the new level of the product will replace the old one. By installing the new level onto a separate target system, you can test the new level, and keep the old one in production at the same time. When you install a product that shares libraries or load modules with other products, the installation can disrupt the other products. By installing the product onto a separate target system, you can assess these impacts without disrupting your production system. 5.1 Driving System Requirements This section describes the environment of the driving system required to install IBM z Systems Development and Test Environment Tools. 5.1.1 Machine Requirements The driving system can run in any hardware environment that supports the required software. 5.1.2 Programming Requirements Figure 3: Driving System Software Requirements 11 IBM z Systems Development and Test Environment Tools

Program Number Product Name Minimum VRM Minimum Service Level will satisfy these APARs 5650-ZOS z/os 02.01.00 N/A No Included in the shipped product? Note: SMP/E is a requirement for installation and an element of z/os, but can also be ordered as a separate product, 5655-G44, minimally V3.6. Note: Installation might require migration to new z/os releases to be service supported. See http://www-03.ibm.com/systems/z/os/zos/support/zos_eos_dates.html. 5.2 Target System Requirements This section describes the environment of the target system required to install and use IBM z Systems Development and Test Environment Tools. IBM z Systems Development and Test Environment Tools install in the z/os (Z038) SREL. 5.2.1 Machine Requirements The target system can run in any hardware environment that supports the required software. 5.2.2 Programming Requirements 5.2.2.1 Installation Requisites: Installation requisites identify products that are required and must be present on the system, or products that are not required but should be present on the system for the successful installation of this product. Mandatory installation requisites identify products that are required on the system for the successful installation of this product. zd&t Tools have no mandatory installation requisites. Conditional installation requisites identify products that are not required for successful installation of this product but can resolve such things as certain warning messages at installation time. These products are specified as IF REQs. IBM z System Development and Test Environment Tools have no conditional installation requisites. 5.2.2.2 Operational Requisites: Operational requisites are products that are required and must be present on the system, or products that are not required but should be present on the system for this product to operate all or parts of its functions. Mandatory operational requisites identify products that are required for this product to operate its basic 12 IBM z Systems Development and Test Environment Tools

functions. IBM z Systems Development and Test Environment Tools have no conditional operational requisites. Conditional operational requisites identify products that are not required for this product to operate its basic functions, but are required at run time for this product to operate specific functions. These products are specified as IF REQs. IBM z Systems Development and Test Environment Tools have no conditional operational requisites. 5.2.2.3 Toleration or Coexistence Requisites: Toleration or coexistence requisites identify products that must be present on sharing systems. These systems can be other systems in a multisystem environment (not necessarily sysplex), a shared DASD environment (such as test and production), or systems that reuse the same DASD environment at different time intervals. IBM z Systems Development and Test Environment Tools have no toleration or coexistence requisites. 5.2.2.4 Incompatibility (Negative) Requisites: Negative requisites identify products that must not be installed on the same system as this product. IBM z Systems Development and Test Environment have no negative requisites. 5.2.3 DASD Storage Requirements IBM z Systems Development and Test Environment Tools libraries can reside on all supported DASD types. Figure 4: Space Requirements. Library Type Total Space Required in 3390 Tracks Target 30 N/A Distribution 30 N/A Notes: File System Description 1. For non-recfm U data sets, IBM recommends using system-determined block sizes for efficient DASD utilization. For RECFM U data sets, IBM recommends using a block size of 32760, which is most efficient from the performance and DASD utilization perspective. 2. Abbreviations used for data set types are shown as follows. U Unique data set, allocated by this product and used only by this product. This table provides all the required information to determine the correct storage for this data set. You do not need to refer to other tables or program directories for the data set size. S Shared data set, allocated by this product and used by this product and other products. To determine the correct storage needed for this data set, add the storage size given in this table to those given in other tables (perhaps in other program directories). If the data set already 13 IBM z Systems Development and Test Environment Tools

E exists, it must have enough free space to accommodate the storage size given in this table. Existing shared data set, used by this product and other products. This data set is not allocated by this product. To determine the correct storage for this data set, add the storage size given in this table to those given in other tables (perhaps in other program directories). If the data set already exists, it must have enough free space to accommodate the storage size given in this table. For more information about the names and sizes of the required data sets, see 6.1.5, Allocate SMP/E Target and Distribution Libraries on page 18. 3. Abbreviations used for the file system path type are as follows. N New path, created by this product. X Path created by this product, but might already exist from a previous release. P Previously existing path, created by another product. 4. All target and distribution libraries listed have the following attributes: The default name of the data set can be changed. The default block size of the data set can be changed. The data set can be merged with another data set that has equivalent characteristics. The data set that contains samples can be either a PDS or a PDSE. The data set that contains program objects must be a PDSE. 5. All target libraries listed have the following attributes: These data sets can be SMS-managed, but they are not required to be SMS-managed. These data sets are not required to reside on the IPL volume. The values in the "Member Type" column are not necessarily actual SMP/E element types that are identified in the SMPMCS. 6. The target library that is listed and contains load modules has the following attributes: This data set can be in the LPA, but is not required to be in the LPA. This data set can be in the LNKLST. This data set is required to be APF-authorized. The following figures describe the target and distribution libraries and file system paths required to install zd&t Tools. Note: Use the data in these tables to determine which libraries can be merged into common data sets. In addition, since some ALIAS names may not be unique, ensure that no naming conflicts will be introduced before merging libraries. Figure 5: Storage Requirements for Target Libraries Library DDNAME Member Type Target Volume TYPE ORG RECFM LRECL No. of 3390 Trks No. of DIR Blks SFEUSAMP Sample Any U PDS FB 80 15 5 SFEUAUTH PROGRAM Any U LIBRARY U 0 15 NOLIMIT 14 IBM z Systems Development and Test Environment Tools

Figure 6: Storage Requirements for Distribution Libraries Library DDNAME Member Type Target Volume TYPE ORG RECFM LRECL No. of 3390 Trks No. of DIR Blks AFEUSAMP Sample Any U PDS FB 80 15 5 AFEUAUTH PROGRAM Any U LIBRARY U 0 15 NOLIMIT 5.3 FMIDs Deleted None. 5.4 Special Considerations None. 15 IBM z Systems Development and Test Environment Tools

6.0 Installation Instructions This chapter describes the installation method and the step-by-step procedures to install and activate the functions of IBM z Systems Development and Test Environment Tools. Please note the following points: If you want to install zd&t Tools into your own SMP/E environment, consult the SMP/E manuals for instructions on creating and initializing the SMPCSI and the SMP/E control data sets. You can use the provided sample jobs to perform part or all of the installation tasks. The SMP/E jobs assume that all DDDEF entries that are required for SMP/E execution have been defined in appropriate zones. You can use the SMP/E dialogs instead of the sample jobs to accomplish the SMP/E installation steps. 6.1 Installing zd&t Tools. 6.1.1 SMP/E Considerations. Use the SMP/E RECEIVE, APPLY, and ACCEPT commands to install this release of zd&t Tools. 6.1.2 SMP/E Options Subentry Values The recommended values for certain SMP/E CSI subentries are shown in Figure 7. Using values lower than the recommended values can result in failures in the installation. DSSPACE is a subentry in the GLOBAL options entry. PEMAX is a subentry of the GENERAL entry in the GLOBAL options entry. See the SMP/E manuals for instructions on updating the global zone. Figure 7: SMP/E Options Subentry Values Subentry Value Comment DSSPACE 1200, 1200, 1400 PEMAX SMP/E default IBM recommends using the SMP/E default for PEMAX. 6.1.3 Upload SMPMCS and RELFILEs Installation materials for z Systems component of zd&t Tools are included in the Tools package that is installed on a Linux system. Once the Linux installation of the Web UI is complete, the directory /opt/ibm/zdt/zsystem contains IBM.HALMB02.** files that must be uploaded to a mainframe for installation. 16 IBM z Systems Development and Test Environment Tools

To ensure that the datasets have correct format (RECFM=FB,LRECL=80), it is recommended to allocate them before uploading the data. The following JCL can be used (edit the job card and replace #hlq with a desired high-level qualifier) //FEUSEQAL JOB <job parameters> //ALLOC PROC LLQ=,TRKS= //ALLOC EXEC PGM=IEFBR14 //DATASET DD DSN=#hlq.IBM.HALMB02.&LLQ, // DISP=(NEW,CATLG), // RECFM=FB,LRECL=80,DSORG=PS,BLKSIZE=0, // UNIT=SYSALLDA, // VOL=SER=, specify a volser if needed // SPACE=(TRK,(&TRKS,5)) //EALLOC PEND //* //RELFILE1 EXEC ALLOC,LLQ=F1.BIN,TRKS=4 //RELFILE2 EXEC ALLOC,LLQ=F2.BIN,TRKS=12 //SMPMCS EXEC ALLOC,LLQ=SMPMCS,TRKS=1 Transfer the installation files to the pre-allocated mainframe datasets in binary mode. Unpack the uploaded hlq.ibm.halmb02.f1.bin dataset by using TSO RECEIVE command: TSO RECEIVE INDA( hlq.ibm.halmb02.f1.bin ) When prompted for restore parameters, reply DSN( hlq.ibm.halmb02.f1 ) Repeat this process to receive hlq.ibm.halmb02.f2 from hlq.ibm.halmb02.f2.bin. After you complete this process, the following datasets will be available: Figure 8: Installation material Data set names: hlq.ibm.halmb02.f1 hlq.ibm.halmb02.f2 hlq.halmb02.smpmcs Description Samples, including installation jobs Programs SMP/E installation statements 6.1.4 Sample Jobs The following sample installation jobs are provided as part of the product to help you install zd&t Tools. All jobs are in the dataset hlq.ibm.halmb02.f1. They all are expected to finish with return code 0. Figure 9: Installation jobs provided Job Name Job Type Description FEU1SMPE SMP/E Create an SMP/E environment (optional) FEU2RCVE RECEIVE SMP/E RECEIVE job FEU3ALOC ALLOCATE Allocate target and distribution libraries FEU4DDEF DDDEF Create SMP/E DDDEF entries FEU5APL APPLY SMP/E APPLY job 17 IBM z Systems Development and Test Environment Tools

FEU6ACPT ACCEPT SMP/E ACCEPT job 6.1.5 Perform SMP/E Allocation If you choose to create a new SMP/E environment for this install, edit and submit FEU1SMPE to allocate and initialize all SMP/E data sets. 6.1.6 Perform SMP/E RECEIVE Edit and submit FEU2RCVE. 6.1.7 Allocate SMP/E Target and Distribution Libraries If you choose to reuse the existing target and distribution libraries, skip this step and proceed to section 6.1.9 for SMP/E APPLY. Edit and submit sample job FEU3ALOC. If you intend to use the target load library to run the product (recommended), it must be APF authorized. 6.1.8 Create SMP/E DDDEF entries Edit and submit the sample job FEU4DDEF. Note that SFEUAUTH library must be APF-authorized. Consider this if you wish to put zd&t programs into a library used by other products. 6.1.9 Perform SMP/E APPLY Edit and submit the job FEU5APL for an APPLY CHECK run. Once the APPLY CHECK is successful, remove the CHECK operand, and run the job again to do the APPLY. 6.1.10 Perform SMP/E ACCEPT Edit and submit the job FEU6ACPT for an ACCEPT CHECK run. Once the ACCEPT CHECK is successful, remove the CHECK operand, and run the job again to do the ACCEPT. 6.1.11 Install Unix System Services Script If you already have a previous version installed, proceed to part 2 of this section to update the script. 1. In Unix System Services command shell, run with UID(0), enter the following commands : 18 IBM z Systems Development and Test Environment Tools

mkdir -p -m 755 /usr/lpp/ibm/zdt ln -e FEUCLI /usr/lpp/ibm/zdt/feucli.el touch /usr/lpp/ibm/zdt/feuc chmod 755 /usr/lpp/ibm/zdt/feuc 2. Edit /usr/lpp/ibm/zdt/feuc to contain the following text. Note that the setting for STEPLIB must match the dataset name for the SFEUAUTH target library, or an alternative APFauthorized load library where you plan to put the executable programs. The target library was allocated in section 6.1.7, job FEU3ALOC. STEPLIB='dsprefix.SFEUAUTH' /usr/lpp/ibm/zdt/feucli.el $@ 6.1.12 Authorize the program library Add the Tools program library, which you specified as the STEPLIB in the preceding step, to the list of APF-authorized libraries. 19 IBM z Systems Development and Test Environment Tools

7.0 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing IBM Corporation North Castle Drive Armonk, New York 10504-1785 USA For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd. 19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan 7.1 Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml. 20 IBM z Systems Development and Test Environment Tools