ibm z open unit test version 1.0: host configuration guide€¦ · open unit t est host system r...

IBM Z Open Unit TestVersion 1.0

Host Configuration Guide

SC27-9413-00

IBM

NoteBefore using this information, be sure to read the general information under “Notices” on page 35.

First edition (March 2019)

This edition applies to IBM Z Open Unit Test Version 1.0 and to all subsequent releases and modifications untilotherwise indicated in new editions.

IBM welcomes your comments. You can send your comments by mail to the following address:

IBM CorporationAttn: Information Development Department 53NABuilding 501 P.O. Box 12195Research Triangle Park NC 27709-2195USA

You can fax your comments to: 1-800-227-5088 (US and Canada)

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in anyway it believes appropriate without incurring any obligation to you.

© Copyright IBM Corporation 2015, 2019.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . vii

About this document . . . . . . . . . ixWho should use this document . . . . . . . . ix

Host Configuration Guide . . . . . . 1

Chapter 1. Planning. . . . . . . . . . 3Migration considerations . . . . . . . . . . 3Planning considerations . . . . . . . . . . 3

Product overview. . . . . . . . . . . . 3Skill requirements . . . . . . . . . . . 4Time requirements . . . . . . . . . . . 4

Preinstallation considerations . . . . . . . . . 4Installation user ID . . . . . . . . . . . 5Requisite products . . . . . . . . . . . 5Required resources . . . . . . . . . . . 5

Preconfiguration considerations . . . . . . . . 6Product selection . . . . . . . . . . . . 7Workload management . . . . . . . . . . 7Resource usage and system limits . . . . . . 7Required configuration of requisite products. . . 8User ID considerations . . . . . . . . . . 8Server considerations . . . . . . . . . . 9

Predeployment considerations . . . . . . . . 9Client checklist . . . . . . . . . . . . . 10

Chapter 2. Basic customization . . . . 13Requirements and checklist . . . . . . . . . 13Customization setup . . . . . . . . . . . 13PARMLIB changes . . . . . . . . . . . . 14

Set the z/OS UNIX definitions in BPXPRMxx . . 14Product enablement in IFAPRDxx . . . . . . 15LINKLIST definitions in PROGxx . . . . . . 17

Requisite LINKLIST and LPA definitions . . . 18PROCLIB changes . . . . . . . . . . . . 18

ELAXF* remote build procedures . . . . . . 19Security definitions . . . . . . . . . . . . 20idz.env, the environment configuration file . . . . 21

Chapter 3. Host-based code analysis 23Requirements and checklist . . . . . . . . . 23Code review . . . . . . . . . . . . . . 23

Modify code review processing . . . . . . . 24Code coverage . . . . . . . . . . . . . 24

Single Code coverage invocation . . . . . . 24Multiple Code coverage invocations . . . . . 24Code coverage output . . . . . . . . . . 25

Chapter 4. Other customization tasks 27z/OS UNIX subprojects . . . . . . . . . . 27

REXEC or SSH setup . . . . . . . . . . 27Include preprocessor support . . . . . . . . 28xUnit support for Enterprise COBOL and PL/I . . 28xUnit support for CICS applications . . . . . . 30

Chapter 5. Security definitions . . . . 31Requirements and checklist . . . . . . . . . 31Define the data set profiles . . . . . . . . . 31Verify the security settings . . . . . . . . . 32

Chapter 6. Migration guide . . . . . . 33Migration considerations . . . . . . . . . . 33

Backing up the previously configured files . . . 33Migrate to version 1.0 . . . . . . . . . . . 33

Notices . . . . . . . . . . . . . . 35Programming interface information . . . . . . 37Trademarks . . . . . . . . . . . . . . 37Terms and conditions for product documentation. . 37

© Copyright IBM Corp. 2015, 2019 iii

iv IBM Z Open Unit Test Version 1.0: Host Configuration Guide

Figures

1. idz.env: environment configuration file 21

© Copyright IBM Corp. 2015, 2019 v

vi IBM Z Open Unit Test Version 1.0: Host Configuration Guide

Tables

1. Required resources . . . . . . . . . . 52. Optional resources . . . . . . . . . . 63. Administrators needed for required tasks 64. Administrators needed for optional tasks 65. Client checklist: Mandatory parts . . . . . 106. Client checklist: Optional parts . . . . . . 10

7. Match load modules to functions . . . . . 178. Sample ELAXF* procedures . . . . . . . 199. ELAXF* high-level qualifier checklist . . . . 20

10. ELAXF* . . . . . . . . . . . . . . 2011. Security setup variables . . . . . . . . 31

© Copyright IBM Corp. 2015, 2019 vii

viii IBM Z Open Unit Test Version 1.0: Host Configuration Guide

About this document

This document discusses the configuration of IBM® Z Open Unit Test on yourz/OS® host system.

The following names are used in this document:v IBM Explorer for z/OS is called z/OS Explorer.v IBM z/OS Debugger is called z/OS Debugger.v IBM Z Open Unit Test is called Z Open Unit Test.v IBM z/OS Automated Unit Testing Framework is called zUnit.v z/OS UNIX System Services is called z/OS UNIX.v Customer Information Control System Transaction Server is called CICSTS,

abbreviated to CICS®.

This document is part of a set of documents that describe Z Open Unit Test hostsystem configuration. Each of these documents has a specific target audience. Tocomplete the Z Open Unit Test configuration, you are not required to read alldocuments.v IBM Z Open Unit Test Host Configuration Guide (this document) describes in detail

all planning tasks, configuration tasks, and options (including optional ones) andprovides alternative scenarios.

v IBM Z Open Unit Test Host Configuration Reference describes Z Open Unit Testdesign and gives background information for various configuration tasks of ZOpen Unit Test, z/OS components, and other products (such as WLM) related toZ Open Unit Test.

For the most up-to-date versions of this document, see the Z Open Unit TestKnowledge Center available at https://www.ibm.com/support/knowledgecenter/SSZHNR/zot_welcome.html.

For the most up-to-date versions of the complete documentation, includinginstallation instructions, white papers, podcasts, and tutorials, see the library pageof the IBM Z Open Unit Test website (https://www.ibm.com/support/docview.wss?uid=ibm10738975).

Who should use this documentThis document is intended for system programmers who are installing andconfiguring IBM Z Open Unit Test.

This document lists in detail the steps that are needed to do a full setup of theproduct, including some non-default scenarios. Background information that canhelp you to plan and execute the configuration can be found in the IBM Z OpenUnit Test Host Configuration Reference. To use this document, you must be familiarwith the z/OS UNIX System Services and MVS™ host systems.

© Copyright IBM Corp. 2015, 2019 ix

https://www.ibm.com/support/knowledgecenter/SSZHNR/zot_welcome.html


https://www.ibm.com/support/docview.wss?uid=ibm10738975

https://www.ibm.com/support/docview.wss?uid=ibm10738975

x IBM Z Open Unit Test Version 1.0: Host Configuration Guide

Host Configuration Guide

© Copyright IBM Corp. 2015, 2019 1

2 IBM Z Open Unit Test Version 1.0: Host Configuration Guide

Chapter 1. Planning

Use the information in this chapter to plan the installation and deployment of ZOpen Unit Test. The following subjects are described:v “Migration considerations”v “Planning considerations”v “Preinstallation considerations” on page 4v “Preconfiguration considerations” on page 6v “Predeployment considerations” on page 9v “Client checklist” on page 10

For a complete list of the Z Open Unit Test hardware and software requirements,including prerequisites and corequisites, see the Software Product CompatibilityReports (SPCR) tool (https://www.ibm.com/software/reports/compatibility/clarity/index.html).

Migration considerationsChapter 6, “Migration guide,” on page 33 describes changes to the installation andconfiguration of this release with respect to previous releases of the product. Usethis information to plan your migration to the current release of Z Open Unit Test.

Planning considerations

Product overviewZ Open Unit Test consists of a client, installed on the user's personal computer,and a server, installed on one or more host systems. Both client and host areinstalled on top of IBM Explorer for z/OS. This documentation containsinformation for a z/OS host system.

The client provides developers with an Eclipse-based development environmentthat facilitates a uniform graphical interface to the host, and that, among otherthings, can offload work from the host to the client, saving resources on the host.

The host portion consists of several permanently active tasks and tasks that arestarted ad hoc. These tasks allow the client to work with the various componentsof your z/OS host system, such as MVS data sets, TSO commands, z/OS UNIXfiles and commands, job submit, and job output. The host components of Z OpenUnit Test are shared by multiple products offered by IBM.

Z Open Unit Test enhances the basic access functionality provided by z/OSExplorer. Z Open Unit Test provides features like rich, language-aware editors witherror feedback.

For information about Z Open Unit Test itself, how it interacts with your system,and with the prerequisite and co-requisite products, see the Z Open Unit Test HostConfiguration Reference. The IBM Explorer for z/OS Host Configuration Reference givessimilar information for z/OS Explorer, which is a requisite for Z Open Unit Test.


https://www.ibm.com/software/reports/compatibility/clarity/index.html


To learn more about the functionality that is offered by Z Open Unit Test, see the ZOpen Unit Test Knowledge Center at https://www.ibm.com/support/knowledgecenter/SSZHNR/zot_welcome.html, or your local IBM representative.

Skill requirementsSMP/E skills are needed for a Z Open Unit Test host installation.

The configuration of Z Open Unit Test requires more than the typical systemprogramming permissions and expertise, so assistance from others might beneeded. Table 3 on page 6 and Table 4 on page 6 list the administrators who areneeded for the required and optional customization tasks.

Time requirementsThe amount of time that is required to install and configure the Z Open Unit Testhost system components depends on various factors such as these:v The current z/OS UNIX and TCP/IP configurationv The availability of prerequisite software and maintenancev The availability of a user, who has successfully installed the client, to test the

installation and report any problems that might occur

Experience has shown that the installation and configuration process for the ZOpen Unit Test host system requires less than one day. This time requirement doesnot include the installation and configuration of IBM Explorer for z/OS, which is arequired product. This time requirement is for a clean installation performed by anexperienced system programmer. If problems are encountered, or if the requiredskills are not available, the setup will take longer.

Preinstallation considerationsFor detailed instructions on the SMP/E installation of the product, see ProgramDirectory for IBM Z Open Unit Test.

The IBM Z Open Unit Test FMIDs are shared by multiple IBM products, so it ispossible you already have installed one or more of the FMIDs. In this case you canreuse the existing installation and go directly to the configuration tasks.

The Z Open Unit Test servers are single-system minded, and are not SYSPLEXaware. If you are using the servers in a SYSPLEX, you must ensure that the datarequested by the end users (data sets, job output, z/OS UNIX files) is available onthe system Z Open Unit Test is installed. See “Predeployment considerations” onpage 9 for cloning Z Open Unit Test to other systems.

To run multiple instances of Z Open Unit Test on a single host system, see"Running multiple instances" in the IBM Explorer for z/OS Host ConfigurationReference.

The file system in which Z Open Unit Test is installed must be mounted with theSETUID permission bit on (this is the system default). Mounting the file system withthe NOSETUID parameter prevents Z Open Unit Test from creating the user's securityenvironment, and rejects the connection requests of the client. The same is true forthe file systems hosting z/OS Explorer, Java™, and z/OS UNIX binaries.




Installation user IDThe user ID that is used to install Z Open Unit Test, or to install maintenance,must have at least the following attributes:v TSO access (with a normal region size).

Note: A large region size is required for the user ID that runs the InstallationVerification Programs (IVPs) because functions requiring a lot of memory (suchas Java) are executed. You should set the region size to 131072 kilobytes (128megabytes) or higher.

v An OMVS segment defined to the security system (for example, RACF®), bothfor the user ID and its default group.– The HOME field must refer to a home directory that is allocated for the user,

with READ, WRITE, and EXECUTE access.– The PROGRAM field in the OMVS segment should be /bin/sh or other valid

z/OS UNIX shell, such as /bin/tcsh.– The user ID’s default group requires a GID.

v UID=0 or READ authorization to the BPX.SUPERUSER profile in the FACILITY class.v If the BPX.FILEATTR.APF or BPX.FILEATTR.PROGCTL profiles are defined in the

FACILITY class, READ access to these profiles.v READ, WRITE, and EXECUTE access to the /tmp directory (or a directory

referenced in the TMPDIR environment variable).

Requisite productsZ Open Unit Test has a list of prerequisite software that must be installed andoperational before the product will work. There is also a list of corequisite softwareto support specific features of Z Open Unit Test. These requisites must be installedand operational at runtime for the corresponding features to work as designed.

For a complete listing of the Z Open Unit Test software requirements includingprerequisites and co-requisites, see the Software Product Compatibility Reports(SPCR) tool (https://www.ibm.com/software/reports/compatibility/clarity/index.html).

Plan ahead to have these requisite products available, as it might take some time,depending on the policies at your site. The key requisites for a basic setup are:v z/OS 2.2 or higherv IBM Explorer for z/OS 3.1v Latest service release of Java 6.0 or higher (31 or 64 bit)

Required resourcesZ Open Unit Test requires the allocation of the systems resources listed in Table 1.The resources listed in Table 2 on page 6 are required for optional services. Plan tohave these resources available because, depending on the policies at your site, itmight take some time to get them.

Table 1. Required resources

Resource Default value Information

MVS build procedures ELAXF* “PROCLIB changes” on page18

Chapter 1. Planning 5



Table 2. Optional resources

Resource Default value Information

port range for host-confineduse

any available port is used v Chapter 3, “Host-basedcode analysis,” on page 23

v “xUnit support for CICSapplications” on page 30

PROCLIB update v AZU*

v AKG*

v “xUnit support forEnterprise COBOL andPL/I” on page 28

v Chapter 3, “Host-basedcode analysis,” on page 23

CICS TS update none “xUnit support for CICSapplications” on page 30

The configuration of Z Open Unit Test requires more than the typical systemprogramming permissions and expertise; therefore, assistance from others might beneeded. Table 3 and Table 4 list the administrators who are needed for the requiredand optional customization tasks.

Table 3. Administrators needed for required tasks

Administrator Task Information

System Typical system programmeractions are required for allcustomization tasks

N/A

Table 4. Administrators needed for optional tasks

Administrator Task Information

Security Define data set profiles "Security considerations" inHost Configuration Reference

TCP/IP Define new TCP/IP ports v “Multiple Code coverageinvocations” on page 24


CICS TS v Update CICS region JCL

v Update CICS region CSD

v Update CICS region SIP

v Define CICS resources


WLM Assign goals to Z Open UnitTest tasks

"WLM considerations" in theHost Configuration Reference

Preconfiguration considerationsFor information about Z Open Unit Test itself, how it interacts with your system,and with the prerequisite and co-requisite products, see the Z Open Unit Test HostConfiguration Reference. The IBM Explorer for z/OS Host Configuration Reference givessimilar information for z/OS Explorer, which is a requisite for Z Open Unit Test.This information can assist you in creating a setup that supports your currentneeds and future growth.


Before configuring Z Open Unit Test, ensure you configured z/OS Explorer.

Product selectionThe host components of Z Open Unit Test are used by different products. When indoubt, contact the person responsible for the purchase of Z Open Unit Test, orpossibly your local IBM representative, to learn which product was purchased.With this information, you can select the correct product registration method, aspricing and available features differ for each of the following products, and thehost components will register only as one of the possible products.

IBM Z Open Development (program number 5737-I22)The Z Open Development client enhances the basic access functionalityprovided by z/OS Explorer. Activation of client features is managed by theclient.

IBM Z Open Unit Test (program number 5737-J31)The Z Open Unit Test client enhances the functionality provided by ZOpen Development. Activation of client features is managed by the client.

IBM Developer for z Systems (program number 5724-T07)The Developer for z Systems client enhances the functionality provided byZ Open Unit Test. Activation of client features is managed by the client.

IBM Developer for z Systems Enterprise Edition (program number 5655-AC5)The Developer for z Systems Enterprise Edition provides the same clientfunctionality as Developer for z Systems. However, activation of clientfeatures is managed by the host, and this product provides additionaldebug related capabilities, such as a 3270 interface.

IBM Application Delivery Foundation for z Systems® (program number5655-AC6)

Application Delivery Foundation for z Systems provides Developer for zSystems Enterprise Edition, which is described earlier, combined with otherproducts useful for z/OS application development activities.

Workload managementUnlike traditional z/OS applications, Z Open Unit Test is not a monolithicapplication that can be identified easily to Workload Manager (WLM). Z OpenUnit Test consists of several components that interact to give the client access tothe host system services and data. To plan your WLM configuration, see "WLMconsiderations" in the Host Configuration Reference.

Note: Z Open Unit Test consists of multiple tasks that communicate with eachother and the client. These tasks use various timers to detect communication losswith their partners. Timeout issues can arise (due to lack of CPU time during thetimeout window) on systems with a heavy CPU load or incorrect WorkloadManagement (WLM) settings for Z Open Unit Test.

Resource usage and system limitsZ Open Unit Test uses a variable number of system resources such as addressspaces, and z/OS UNIX processes and threads. The availability of these resourcesis limited by various system definitions. To estimate the usage of key resources sothat you can plan your system configuration, see "Tuning considerations" in theIBM Explorer for z/OS Host Configuration Reference. Z Open Unit Test can run ineither 31-bit or 64-bit mode, changing the storage resource limitations drastically.


Required configuration of requisite productsConsult your MVS system programmer, security administrator, and TCP/IPadministrator to verify if the requisite products and software are installed, tested,and working. Some requisite customization tasks that can be overlooked are listedhere:v All Z Open Unit Test users must have READ and EXECUTE access to the Java

directories.v Ensure that at least the basic configuration of z/OS Explorer has completed,

since Z Open Unit Test customization extends this setup.

User ID considerationsThe user ID of a Z Open Unit Test user must have at least the following attributes:v TSO access (with a normal region size).

Note: A large region size is required for the user ID that runs the InstallationVerification Programs (IVPs) because functions requiring a lot of memory (suchas Java) are executed. You should set the region size to 131072 kilobytes (128megabytes) or higher.

v An OMVS segment defined to the security system (for example, RACF), both forthe user ID and its default group.– The HOME field must refer to a home directory allocated for the user (with

READ, WRITE and EXECUTE access).– The PROGRAM field in the OMVS segment should be /bin/sh or other valid

z/OS UNIX shell, such as /bin/tcsh.– The ASSIZEMAX field should not be set, so that system defaults are used.– The user ID does not require UID 0.

Example (command LISTUSER userid NORACF OMVS):USER=userid

OMVS INFORMATION----------------UID= 0000003200HOME= /u/useridPROGRAM= /bin/shCPUTIMEMAX= NONEASSIZEMAX= NONEFILEPROCMAX= NONEPROCUSERMAX= NONETHREADSMAX= NONEMMAPAREAMAX= NONE

– The user ID’s default group requires a GID.Example (command LISTGRP group NORACF OMVS):GROUP group

OMVS INFORMATION----------------GID= 0000003243

v READ and EXECUTE access to the z/OS Explorer and Z Open Unit Testinstallation and configuration directories and files, default /usr/lpp/IBM/zexpl/*, /etc/zexpl/*, /var/zexpl/*, /usr/lpp/IBM/idz/*, and /var/idz/*.

v READ, WRITE, and EXECUTE access to the z/OS Explorer WORKAREAdirectory, default /var/zexpl/WORKAREA, and user log directory, default/var/zexpl/logs.


v READ access to the z/OS Explorer and Z Open Unit Test installation data sets,default FEK.SFEK* and FEL.SFEL*.

v READ, WRITE, and EXECUTE access to the /tmp directory or a directoryreferenced in the TMPDIR environment variable.

Server considerationsz/OS Explorer and Z Open Unit Test consists of multiple permanently activeservers, which can be started tasks or user jobs. These servers provide therequested services themselves or start other servers (as z/OS UNIX threads or userjobs) to provide the service. There is no specific startup order.

The only requirement is that the servers are up and running before the first usertries to connect. The security mechanisms used by z/OS Explorer and Z Open UnitTest servers and services rely on the data sets and file systems they reside in beingsecure. This implies that only trusted system administrators should be able toupdate the program libraries and configuration files.

Predeployment considerationsZ Open Unit Test supports the cloning of an installation to a different system, thusavoiding the need for a SMP/E installation on each system.

The following data sets, directories, and files are mandatory for deployment toother systems. If you copied a file to a different location, this file must replace itscounterpart in the following lists.

Note: The following list does not cover the deployment needs of the prerequisiteand co-requisite software (including z/OS Explorer).

Z Open Unit Testv FEL.SFELLOAD(*)v FEL.SFELPROC(*)v FEL.#CUST.PROCLIB(*)v /usr/lpp/IBM/idz/*v /var/idz/*v /etc/zexpl/*

Z Open Unit Test Host Utilitiesv AKG.SAKGPROC(*)v /usr/lpp/IBM/idzutil/*

Notes:

v FEL and /usr/lpp/IBM/idz are the high-level qualifier and path used during theinstallation of the Z Open Unit Test. FEL.#CUST, /etc/zexpl and /var/idz are thedefault locations used during the customization of the product where/etc/zexpl is the z/OS Explorer configuration directory.

v AKG and /usr/lpp/IBM/idzutil are the high-level qualifier and path used duringthe installation of Z Open Unit Test Host Utilities.

v You should install Z Open Unit Test in a private file system, possibly combinedwith z/OS Explorer, to ease the deploying of the z/OS UNIX parts of theproduct. If you cannot use a private file system, use an archiving tool such asthe z/OS UNIX tar command to transport the z/OS UNIX directories from one


system to another. This method is required for preserving the attributes (such asprogram control) of the Z Open Unit Test files and directories.For more information about the following sample commands to archive andrestore the Z Open Unit Test installation directory, see UNIX System ServicesCommand Reference (SA22-7802).– Archive: cd /SYS1/usr/lpp/IBM/idz; tar -cSf /u/userid/idz.tar– Restore: cd /SYS2/usr/lpp/IBM/idz; tar -xSpf /u/userid/idz.tar

Client checklist

Users of the Z Open Unit Test client must know the result of certain host systemcustomizations, such as TCP/IP port numbers, for the client to work properly. Usethese checklists to gather the information needed.

The checklist in Table 5 lists the required results of mandatory customization steps.Table 6 lists the required results of optional customization steps.

Table 5. Client checklist: Mandatory parts

Customization Value

(prerequisite) RSE daemon TCP/IP port number. The default is 4035.

This port is set during z/OS Explorer configuration.

Table 6. Client checklist: Optional parts

Customization Value

Location of the ELAXF* procedures if they are not in a system procedurelibrary. The default is FEL.#CUST.PROCLIB.

See the note on JCLLIB in “ELAXF* remote build procedures” on page 19.

Procedure or step names of the ELAXF* procedures if they were changed.

See the note on changing them in “ELAXF* remote build procedures” onpage 19.

Location of the AKGCR procedure if it is not in a system procedure library.The default is AKG.#CUST.PROCLIB.

See the note on JCLLIB in “Code review” on page 23.

Location of the AKGCC procedure if it is not in a system procedure library.The default is AKG.#CUST.PROCLIB.

See the note on JCLLIB in “Code coverage” on page 24.

Location of the FEKRNPLI Include Preprocessor exec statement. The defaultis FEL.#CUST.CNTL.

See “Include preprocessor support” on page 28.

Location of the unit test load modules if not in LINKLIST or STEPLIB ofidz.env. The default is FEL.SFELLOAD.

See “xUnit support for Enterprise COBOL and PL/I” on page 28.

Location of the AZUZUNIT procedure if it is not in a system procedurelibrary. The default is FEL.#CUST.PROCLIB.

See the note on JCLLIB in “xUnit support for Enterprise COBOL andPL/I” on page 28.


Table 6. Client checklist: Optional parts (continued)

Customization Value

Location of the sample *.xsd and *.xsl XML files used for unit testoutput formatting. The defaults are /usr/lpp/IBM/idz/samples/zunit/xsdand /usr/lpp/IBM/idz/samples/zunit/xsl.

See “xUnit support for Enterprise COBOL and PL/I” on page 28.

TCP/IP port number for unit test CICS recorder (recording service). Thereis no default.

See “xUnit support for CICS applications” on page 30.

(co-requisite) TN3270 port number for Host Connect Emulator. Thedefault is 23.

See "TCP/IP ports" in Host Configuration Reference.

(co-requisite) REXEC or SSH port number, which, by default are 512 or22.

See “z/OS UNIX subprojects” on page 27.


Chapter 2. Basic customization

The following customization steps are common for the various Z Open Unit Testservices. See the chapters about the specific components for their customizationrequirements.

Requirements and checklistYou need the assistance of a security administrator to complete this customizationtask, which requires the following resources and special customization tasks:v Various PARMLIB updatesv Various PROCLIB updatesv Various security software updates

To verify the installation and to start using Z Open Unit Test at your site, do thefollowing tasks. Unless otherwise indicated, all tasks are mandatory.1. Create customizable copies of samples and create the work environment for Z

Open Unit Test. For details, see “Customization setup.”2. Update SYS1.PARMLIB definitions. For details, see “PARMLIB changes” on page

14.3. Create SYS1.PROCLIB procedures. For details, see “PROCLIB changes” on page

18.4. Update security definitions. For details, see “Security definitions” on page 20.5. Customize Z Open Unit Test configuration files. For details, see “idz.env, the

environment configuration file” on page 21.

Customization setupZ Open Unit Test contains several sample configuration files and sample JCL. Toavoid overwriting your customizations when applying maintenance, copy all ofthese members and z/OS UNIX files to a different location, and customize thecopy.

The Z Open Unit Test FMIDs are shared by multiple IBM products, so it is possibleyou see configurable files, libraries, or directories that are not applicable to yoursetup. When in doubt, refer back to this document, as it contains all information onthe parts that do apply to your setup.

To create customizable copies of configuration files and configuration JCL, and tocreate required z/OS UNIX directories, customize and submit the sample FELSETUPmember in the FEL.SFELSAMP data set. The required customization steps aredescribed within the member.

This job performs the following tasks:v Create FEL.#CUST.PARMLIB and populate it with sample configuration files.v Create FEL.#CUST.PROCLIB and populate it with sample SYS1.PROCLIB members.v Create FEL.#CUST.JCL and populate it with sample configuration JCL.v Create FEL.#CUST.CNTL and populate it with sample server startup scripts.v Create FEL.#CUST.ASM and populate it with sample assembler source code.


v Create FEL.#CUST.SQL and populate it with sample SQL command files.v Populate the z/OS Explorer configuration directory, /etc/zexpl/* with sample

configuration files.v Create /var/idz/* as work directories for various Z Open Unit Test functions,

and populate it with sample files.

Notes:

v The customization steps described here, including the FELSETUP tool, assume thatthe configuration of z/OS Explorer has already been completed.

v The configuration steps in this publication use the member and file locationscreated by the FELSETUP job, unless noted otherwise. The original samples, whichshould not be updated, are in FEL.SFELSAMP and /usr/lpp/IBM/idz/samples/.

v For more details on which sample members are copied to which data set, andfor more details on which directories are created, their permission bitmask, andwhere the various sample files are copied to, see the comments inFEL.SFELSAMP(FELSETUP).

v To aid in migrating an existing setup, the comments in FEL.SFELSAMP(FELSETUP)also document the changes between different versions of Z Open Unit Test.

PARMLIB changesThe following PARMLIB changes are documented in this section:v “Set the z/OS UNIX definitions in BPXPRMxx”v “Product enablement in IFAPRDxx” on page 15v “LINKLIST definitions in PROGxx” on page 17v “Requisite LINKLIST and LPA definitions” on page 18

For more information about the PARMLIB definitions listed in the next sections,see MVS Initialization and Tuning Reference (SA22-7592). For more information aboutthe sample console commands, see MVS System Commands (SA22-7627).

Set the z/OS UNIX definitions in BPXPRMxx

Note:

v During the SMP/E install of Z Open Unit Test, you were advised to place thecode in a separate file system (zFS of HFS) and update BPXPRMxx to mount thisfile system during system IPL. Included is a repeat of the sample mountcommand in case this update still must be done:MOUNT FILESYSTEM(’#dsn’)

MOUNTPOINT(’-PathPrefix-usr/lpp/IBM/idz’)MODE(RDWR) /* can be MODE(READ) */TYPE(ZFS) PARM(’AGGRGROW’) /* zFS, with extents */

/* TYPE(HFS) */ /* HFS, auto. extent */

v During the SMP/E install of Z Open Unit Test Host Utilities, you were advisedto place the code in a separate file system (zFS of HFS) and update BPXPRMxx tomount this file system during system IPL. Included is a repeat of the samplemount command in case this update still must be done:MOUNT FILESYSTEM(’#dsn’)

MOUNTPOINT(’-PathPrefix-usr/lpp/IBM/idzutil’)MODE(RDWR) /* can be MODE(READ) */TYPE(ZFS) PARM(’AGGRGROW’) /* zFS, with extents */

/* TYPE(HFS) */ /* HFS, auto. extent */


Product enablement in IFAPRDxxThe host components of Z Open Unit Test are used by different products. When indoubt, contact the person responsible for the purchase of Z Open Unit Test, orpossibly your local IBM representative, to learn which product was purchased.With this information, you can select the correct product registration method, aspricing and available features differ for each of the following products, and thehost components will register only as one of the possible products.

IBM Z Open Development (program number 5737-I22)The Z Open Development client enhances the basic access functionalityprovided by z/OS Explorer. Activation of client features is managed by theclient.

IBM Z Open Unit Test (program number 5737-J31)The Z Open Unit Test client enhances the functionality provided by ZOpen Development. Activation of client features is managed by the client.

IBM Developer for z Systems (program number 5724-T07)The Developer for z Systems client enhances the functionality provided byZ Open Unit Test. Activation of client features is managed by the client.

IBM Developer for z Systems Enterprise Edition (program number 5655-AC5)The Developer for z Systems Enterprise Edition provides the same clientfunctionality as Developer for z Systems. However, activation of clientfeatures is managed by the host, and this product provides additionaldebug related capabilities, such as a 3270 interface.

IBM Application Delivery Foundation for z Systems (program number5655-AC6)

Application Delivery Foundation for z Systems provides Developer for zSystems Enterprise Edition, which is described earlier, combined with otherproducts useful for z/OS application development activities.

Products to be enabled on z/OS are defined in SYS1.PARMLIB(IFAPRDxx). DefinePROD=xx in the IEASYSxx parmlib member to specify which IFAPRDxx parmlibmember should be used during IPL.

The Z Open Unit Test host components will attempt to register using the followingorder of product definitions. The process stops on the first successful registration.

Specify the following in IFAPRDxx to define IBM Application Delivery Foundationfor z Systems (product code 5655-AC6):PRODUCT OWNER(’IBM CORP’)

NAME(’IBM APP DLIV FND’)ID(5655-AC6)VERSION(*) RELEASE(*) MOD(*)FEATURENAME(*)STATE(ENABLED)

Specify the following in IFAPRDxx to define IBM Developer for z SystemsEnterprise Edition (product code 5655-AC5):PRODUCT OWNER(’IBM CORP’)

NAME(’IBM IDz EE’)ID(5655-AC5)VERSION(*) RELEASE(*) MOD(*)FEATURENAME(*)STATE(ENABLED)

Chapter 2. Basic customization 15

Specify the following in IFAPRDxx to define IBM Developer for z Systems(product code 5724-T07):PRODUCT OWNER(’IBM CORP’)

NAME(’IBM IDz’)ID(5724-T07)VERSION(*) RELEASE(*) MOD(*)FEATURENAME(*)STATE(ENABLED)

Specify the following in IFAPRDxx to define IBM Z Open Unit Test (product code5737-J31):PRODUCT OWNER(’IBM CORP’)

NAME(’IBM Z Open Unit Test’)ID(5737-J31)VERSION(*) RELEASE(*) MOD(*)FEATURENAME(*)STATE(ENABLED)

Specify the following in IFAPRDxx to define IBM Z Open Development (productcode 5737-I22):PRODUCT OWNER('IBM CORP')

NAME('IBM Z Open Dev')ID(5737-I22)VERSION(*) RELEASE(*) MOD(*)FEATURENAME(*)STATE(ENABLED)

After the IFAPRDxx parmlib member is updated, it can be activated dynamically(until the next IPL) with the following console command:SET PROD=xx

Note: All product flavors of the host components register the following features:v FEL-RSED (for RSE daemon in Z Open Unit Test, FMID HHOPxxx)v AKG-CC (for Code Coverage in Z Open Unit Test Host Utilities, FMID

HAKGxxx)v AKG-CR (for Code Review in Z Open Unit Test Host Utilities, FMID HAKGxxx)

A product that is not defined in IFAPRDxx, or defined with STATE(DISABLED) orSTATE(NOTDEFINED) will not be selected for registration. If none of the documentedproducts is defined in IFAPRDxx, Z Open Unit Test will only provide basic servicesfor clients with a valid activation token.

If you change how a product is purchased, for example, you upgrade from using astand-alone version to the IBM Application Delivery Foundation for z Systemsproduct bundle, you must explicitly remove the existing product definition fromthe in-storage tables kept by z/OS when activating the new definition. Follow thisscenario to do this dynamically (without IPL):1. In IFAPRDxx, define the new product as described before, and update the old

product with STATE(DISABLED).2. Activate the update with operator command SET PROD=xx.3. Restart the RSED server to pick up the change.4. You can now safely remove the old product definition from IFAPRDxx.

IBM advises against defining IFAPRDxx entries that have NAME(*) or ID(*) fields,because this will result in ALL z/OS applications that utilize product registrationto find a match on the first test, and adhere to the related STATE() definition. For Z


Open Unit Test with STATE(ENABLED), this means that the application will registeras IBM Application Delivery Foundation for z Systems (product code 5655-AC6).

LINKLIST definitions in PROGxxLINKLIST definitions for Z Open Unit Test can be grouped in two categories:v Z Open Unit Test load libraries that are needed for Z Open Unit Test functions.

These definitions are described in this section.v Requisite load libraries that are needed for Z Open Unit Test functions. These

definitions are described in “Requisite LINKLIST and LPA definitions” on page18.

Table 7. Match load modules to functions. This table describes the functions of loadmodules and the load libraries where they are located.

Load library Load modules Usage STEPLIB

FEL.SFELLOAD ELAX* “ELAXF* remote buildprocedures” on page 19

(error feedback and includepreprocessor)

ELAXF* procedures

FEL.SFELLOAD AZU* andIAZU*

“xUnit support forEnterprise COBOL andPL/I” on page 28

idz.env or MVS batch

In order for the listed Z Open Unit Test services to work, all modules documentedin Table 7 that are related to the service must be made available either throughSTEPLIB or LINKLST (or LPA). See the STEPLIB column in Table 7 if you chooseto use STEPLIB to learn where the STEPLIB definition must be made. However,you should be aware of the following things:v Using STEPLIB in z/OS UNIX has a negative performance impact.v If one STEPLIB library is APF-authorized, then all must be authorized. Libraries

lose their APF authorization when they are mixed with non-authorized librariesin STEPLIB.

v Libraries added to the STEPLIB DD in a JCL are not propagated to the z/OSUNIX processes started by the JCL.

LINKLIST data sets are defined in SYS1.PARMLIB(PROGxx), if your site followed IBMrecommendations. Define PROG=xx in the IEASYSxx parmlib member to specifywhich PROGxx parmlib member should be used during IPL.

The required definitions will look like the following, where listname is the nameof the LINKLIST set that will be activated, and volser is the volume on which thedata set resides if it is not cataloged in the master catalog:v LNKLST ADD NAME(listname) DSNAME(FEL.SFELLMOD) VOLUME(volser)

v LNKLST ADD NAME(listname) DSNAME(FEL.SFELLOAD)

LINKLIST definitions can be created dynamically (until the next IPL) with thefollowing actions:1. Create a new PARMLIB member named PROGxx, for example PROGLL.2. Place the following commands in your new PROGxx member, where volser is

the volume on which the data set resides if it is not cataloged in the mastercatalog:v LNKLST DEFINE,NAME=LLTMP,COPYFROM=CURRENT


v LNKLST ADD NAME=LLTMP,DSN=FEL.SFELLMOD,VOL=volser

v LNKLST ADD NAME=LLTMP,DSN=FEL.SFELLOAD

v LNKLST ACTIVATE,NAME=LLTMP

3. Activate the new definitions by issuing the SET PROG=xx console command,where xx matches the last 2 characters of your new PROGxx member name.

Requisite LINKLIST and LPA definitionsThe following additional libraries must be made available, either through STEPLIBor LINKLIST/LPA, to support the use of optional services. This list does notinclude data sets that are specific to a product that Z Open Unit Test interacts with,like z/OS Explorer:v System load library

– SYS1.LINKLIB

v Language Environment® runtime– CEE.SCEERUN

– CEE.SCEERUN2

v C++'s DLL class library– CBC.SCLBDLL

v System load library (for Enterprise COBOL and PL/I unit test)– SYS1.CSSLIB

– SYS1.SIXMLOD1

Note:

v All libraries that are loaded into LPA are automatically considered to beAPF-authorized and program controlled. Ensure you have proper securitycontrols in place for these libraries.

v Some of the prerequisite and co-requisite products, such as z/OS Explorer, alsorequire STEPLIB or LINKLIST/LPA definitions. See the related productcustomization guides for more information.

LINKLIST data sets are defined in SYS1.PARMLIB(PROGxx) by default. LPA data setsare defined in SYS1.PARMLIB(LPALSTxx).

If you opt to use STEPLIB, you must define the libraries not available throughLINKLIST/LPA in the STEPLIB directive of rse.env, the RSE configuration file. Beaware, however, of these things:v Using STEPLIB in z/OS UNIX has a negative performance impact.v If one STEPLIB library is APF-authorized, then all the other STEPLIB libraries

must be authorized. Libraries lose their APF authorization when they are mixedwith non-authorized libraries in STEPLIB.

v Libraries added to the STEPLIB DD in a JCL are not propagated to the z/OSUNIX processes started by the JCL.

PROCLIB changesThe following PROCLIB changes are documented in this section:v “ELAXF* remote build procedures” on page 19

The remote build procedures listed in the following sections must reside in asystem procedure library defined to your JES subsystem. In the instructions in thefollowing sections, the IBM default procedure library, SYS1.PROCLIB, is used.


ELAXF* remote build proceduresZ Open Unit Test provides sample JCL procedures that can be used for the JCLgeneration, remote project builds, and remote syntax check features of COBOL andPL/I programs. These procedures allow installations to apply their own standards,and ensure that developers use the same procedures with the same compileroptions and compiler levels.

The sample procedures and their function are listed in Table 8.

Table 8. Sample ELAXF* procedures

Member Purpose

ELAXF Include member that specifies variables used by the remote buildprocedures.

ELAXFASM Sample procedure for assembling High Level assembler programs.

ELAXFBMS Sample procedure for creating CICS BMS object and corresponding copy,dsect, or include member. (3)

ELAXFCOC Sample procedure for COBOL compiling and doing Integrated CICStranslate and integrated DB2® translate. (1)

ELAXFCOT Sample procedure for CICS translation for EXEC CICS statementsembedded in COBOL programs.

ELAXFCP1 Sample procedure for COBOL compiling with SCM preprocessorstatements (-INC and ++INCLUDE). (1)

ELAXFDCL Sample procedure for running a program in TSO mode.

ELAXFGO Sample procedure for the GO step.

ELAXFLNK Sample procedure for linking C/C++, COBOL. PLI and High LevelAssembler programs. (1) (3)

ELAXFMFS Sample procedure for creating IMS MFS screens.

ELAXFPLT Sample procedure for doing CICS translation of EXEC CICS statementsembedded in PLI programs.

ELAXFPL1 Sample procedure for PL/I compiling, and integrated CICS translationand integrated DB2 translation. (1)

ELAXFPP1 Sample procedure for PL/I compiling with SCM preprocessor statements(-INC and ++INCLUDE). (1)

ELAXFUOP Sample procedure for generating the UOPT step when building programsthat run in CICS or IMS subsystems.

All remote build procedures rely on the ELAXF include member for the definition ofcommon high-level qualifiers. Customize the sample include member,FEL.#CUST.PROCLIB(ELAXF) as described within the member. You can use Table 9 onpage 20 to assist with this customization.

Review the sample build procedure members, FEL#CUST.PROCLIB(ELAXF*), andcustomize them if required. Some sample ELAXF* procedures in Table 8 are markedwith a footnote as they are more likely to require customization:1. These remote build procedures have commented out references to CICS and

DB2 load libraries.2. These remote build procedures have a reference to a customized input file with

SQL commands.3. These remote build procedures have miscellaneous customizable options.


The names of the procedures and the names of the steps in the procedures matchthe default properties that are included with the Z Open Unit Test client. If thename of a procedure or the name of a step in a procedure is changed, thecorresponding properties file on all of the clients must be updated. You should notchange the procedure and step names.

Table 9. ELAXF* high-level qualifier checklist

Product Default HLQ Value

Z Open Unit Test FEL

Debugger EQAW

COBOL IGY.V5R2M0

PL/I PLI.V4R2M0

LE CEE

CICS CICSTS52.CICS

IMS (site specific libraries) IMS

system LINKLIB SYS1

system MACLIB SYS1

system CSSLIB SYS1

Some ELAXF* procedures reference data set names that do not have fixed low-levelqualifiers. An example is the DB2 runtime library, which holds DB2 utilities thatare compiled by your DB2 administrator. Use Table 10 to map the default data setnames to the names used at your site.

Table 10. ELAXF*. fully qualified data set checklist

Product Default DSN Value

DB2 runtime libraries DSNA11.RUNLIB.LOAD

Once the ELAXF* members are customized, copy them to SYS1.PROCLIB. Ensure thatthe ELAXF include member remains with the ELAXF* build procedures. If themembers cannot be copied into a system procedure library, ask the Z Open UnitTest users to add a JCLLIB card (right after the JOB card) to the job properties onthe client.//MYJOB JOB <job parameters>//PROCS JCLLIB ORDER=(FEL.#CUST.PROCLIB)

Security definitionsTo create the security definitions for Z Open Unit Test, customize and submit thesample FELRACF member. The user submitting this job must have securityadministrator privileges, such as being RACF SPECIAL.

FELRACF is located in FEL.#CUST.JCL, unless you specified a different location whenyou customized and submitted the FEL.SFELSAMP(FELSETUP) job. For more details,see “Customization setup” on page 13.

The following list of security-related definitions for Z Open Unit Test are discussedin detail in Chapter 5, “Security definitions,” on page 31.v Define data set profilesv Verify the security settings


idz.env, the environment configuration fileThe z/OS Explorer RSE server processes (RSE daemon, RSE thread pool, and RSEserver) use the definitions in idz.env to learn about Z Open Unit Test environmentvariables.

idz.env is located in /etc/zexpl/, unless you specified a different location whenyou customized and submitted the FEL.SFELSAMP(FELSETUP) job. For more details,see “Customization setup” on page 13. You can edit the file with the TSO OEDITcommand.

The Z Open Unit Test FMIDs are shared by multiple IBM products, and some ofthe variables in idz.env do not apply to Z Open Unit Test. When in doubt, referback to this document, as it contains all information on the variables that do applyto your setup.

See the following sample idz.env file, which can be customized to match yoursystem environment. Default values are provided for all variables that are notexplicitly specified. The syntax of the file follows standard z/OS UNIX shell syntaxrules. For example, comments start with a number sign (#) when using a US codepage, and spaces around the equal sign (=) are not supported.

Note: For your changes to take effect, the z/OS Explorer RSED started task mustbe restarted.

The following definitions are optional. If omitted, default values are used.

IDZ_HOME Z Open Unit Test home directory. The default is /usr/lpp/IBM/idz.Uncomment and change to match your Z Open Unit Test installation.

IDZ_HLQThe high-level qualifier used to install Z Open Unit Test. The default isFEL. Uncomment and change to match the location of your Z Open UnitTest data sets.

_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DRIS_BUFFER=8"Buffer size, in megabytes, used during remote index creation. The defaultis 8 MB. To change the buffer size, uncomment and customize. Valid valuesare whole numbers between 1 and 2000 (both inclusive). A bigger buffer

#IDZ_HOME=/usr/lpp/IBM/idz#IDZ_HLQ=FEL

## remote index search#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DRIS_BUFFER=8"#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDISABLE_REMOTE_INDEX_SEARCH="

## system#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDISABLE_DELETE_IN_SUBPROJECT=true"

## zUnit unit test#STEPLIB=$STEPLIB:$IDZ_HLQ.SFELLOAD#STEPLIB=$STEPLIB:SYS1.CSSLIB:SYS1.SIXMLOD1

## RTC user build#IDZ_UBLD_DD=$CGI_ISPCONF/ISPF.conf#IDZ_UBLD_STEPLIB=$STEPLIB

Figure 1. idz.env: environment configuration file


speeds up index creation, but uses a bigger portion of the thread pool'sJava heap. The buffer is automatically flushed to the index if it is fullbefore index creation ends.

_RSE_JAVAOPTS="$_RSE_JAVAOPTS-DDISABLE_REMOTE_INDEX_SEARCH="

Disable the Remote Index Search menu item on the client. The default is .To remote indexes for host system data sets, uncomment and specify .

#_RSE_JAVAOPTS="$_RSE_JAVAOPTS-DDISABLE_DELETE_IN_SUBPROJECT=true"

Disable the Delete menu item in the context menu of z/OS subprojects.The default is false. To prevent users from using the Delete menu item inthe context menu of z/OS subprojects, uncomment and specify true.

STEPLIBAccess MVS data sets not in LINKLIST/LPA. The default is NONE.

You can bypass the need of having prerequisite libraries in LINKLIST/LPAby uncommenting and customizing one or more of the following STEPLIBdirectives. For more information about the usage of the libraries in thefollowing list, see “PARMLIB changes” on page 14:# SCLM Developer ToolkitSTEPLIB=$STEPLIB:$IDZ_HLQ.SFELLOAD# zUnit, xUnit support for Enterprise COBOL and PL/ISTEPLIB=$STEPLIB:$IDZ_HLQ.SFELLOAD:SYS1.CSSLIB:SYS1.SIXMLOD1

Note:

v Using STEPLIB in z/OS UNIX has a negative performance impact.v If one STEPLIB library is APF-authorized, then all the other STEPLIB

libraries must be authorized. Libraries lose their APF authorization whenthey are mixed with non-authorized libraries in STEPLIB.

v Libraries that are designed for LPA placement might require additionalprogram control and APF authorizations if they are accessed throughLINKLIST or STEPLIB.

v Coding a STEPLIB DD statement in the server JCL does not set therequested STEPLIB concatenation.

IDZ_UBLD_DDSpecifies the DD statements that will be used when generating JCL for IBMRational Team Concert™ user builds from a Z Open Unit Test client thatinvoke TSO or ISPF commands. By default, Z Open Unit Test uses thedefinitions in ISPF.conf, which is referenced by CGI_ISPCONF in idz.env.Uncomment and change to use the DD definitions in the specified file,which must follow the syntax rules specified for ISPF.conf in IBM Explorerfor z/OS Host Configuration Guide.

IDZ_UBLD_STEPLIBSpecifies the STEPLIB statement that will be used when generating JCL forIBM Rational Team Concert user builds from a Z Open Unit Test client thatinvoke TSO or ISPF commands. By default, Z Open Unit Test uses theSTEPLIB definition in idz.env. Uncomment and change to use the specifiedSTEPLIB definition.


Chapter 3. Host-based code analysis

Similar to the Z Open Unit Test client, the Z Open Unit Test host supports runningcode analysis tools, which are provided as a separate product, IBM Z Open UnitTest Host Utilities. A benefit of doing code analysis on the host is that it can beintegrated in your daily batch processing.

The following code analysis tools are available on the host:v Code review: Using rules with different severity levels, code review scans source

code and reports rule violations.v Code coverage: Analyze a running program and generate a report of lines that

are executed, compared to the total number of executable lines.

Requirements and checklistYou do not need assistance of other administrators to start using host-based codeanalysis tools at your site, but you must perform the following tasks. Unlessotherwise indicated, all tasks are mandatory.1. Install IBM Z Open Unit Test Host Utilities, as documented in Program Directory

for IBM Z Open Unit Test Host Utilities (GI13-2864). When using the provideddefaults, the product is installed using high-level qualifier AKG and z/OS UNIXpath /usr/lpp/IBM/idzutil.

2. Create customizable copies of the provided samples by customizing andsubmitting AKG.SAKGSAMP(AKGSETUP). This job performs the following tasks:v Create AKG.#CUST.PROCLIB and populate it with sample SYS1.PROCLIB

members.v Create AKG.#CUST.JCL and populate it with sample configuration JCL.

Note: IBM z/OS Debugger is a prerequisite for the Code coverage component. TheIBM z/OS Debugger FMID is provided together with the IBM Z Open Unit TestFMIDs.

Code reviewCode review scans source code and reports rule violations, using rules withdifferent severity levels. The tool comes with rule providers for COBOL and PL/I,but other rule providers can be added.

Z Open Unit Test Host Utilities provides a sample procedure, AKGCR, to simplifythe calling of code review services in batch mode. AKGCR is found inAKG.#CUST.PROCLIB, unless you specified a different location when you customizedand submitted the AKG.SAKGSAMP(AKGSETUP) job.

Customize the sample procedure, AKG.#CUST.PROCLIB(AKGCR), as described withinthe member, and copy it to SYS1.PROCLIB.

If the AKGCR procedure cannot be copied into a system procedure library, ask the ZOpen Unit Test users to add a JCLLIB card right after the JOB card to their callingjob.//MYJOB JOB <job parameters>//PROCS JCLLIB ORDER=(AKG.#CUST.PROCLIB)


Modify code review processingZ Open Unit Test Code Review allows for third-party code to be part of the reviewprocess. For example, you can provide a rule provider to analyze C/C++ code, oryou can enhance the Cobol rule provider to recognize site-specific codingconventions.

Host-based code review is an Eclipse process, just like the Z Open Unit Test client.Therefore, the enhancements done by your development support team for codereview on the client can be reused on the host.

The enhancements will consist of Eclipse plugins or Eclipse features. In order toactivate them, you must make them available to the existing code, as documentedin the AKGCRADD configuration job. AKGCRADD is in AKG.#CUST.JCL, unless youspecified a different location when you customized and submitted theAKG.SAKGSAMP(AKGSETUP) job.

Code coverageCode coverage analyzes a running program and generates a report of lines that areexecuted, compared to the total number of executable lines. Note that Codecoverage sets up a TCP/IP connection, using an ephemeral port, with IBM z/OSDebugger, or with the Debug Engine of a Z Open Unit Test client.

Z Open Unit Test Host Utilities provides two ways to invoke Code coverage inbatch mode, A sample JCL procedure, to process a single program run, and a set ofscripts to start and stop a permanently active Code coverage collector that canprocess multiple program runs.

Single Code coverage invocationThe AKGCC sample procedure provides a method to start a Code coverage collector,have it analyze a single program run, stop the collector and archive the results forlater usage.

AKGCC is in AKG.#CUST.PROCLIB, unless you specified a different location when youcustomized and submitted the AKG.SAKGSAMP(AKGSETUP) job.

Customize the sample procedure, AKG.#CUST.PROCLIB(AKGCC), as described withinthe member, and copy it to SYS1.PROCLIB.

If the AKGCC procedure cannot be copied into a system procedure library, ask the ZOpen Unit Test users to add a JCLLIB card right after the JOB card to their callingjob.//MYJOB JOB <job parameters>//PROCS JCLLIB ORDER=(AKG.#CUST.PROCLIB)

Multiple Code coverage invocationsDepending on how your software development process is set up, the convenienceof having the AKGCC procedure take care of everything might not outweigh theresource and time usage to start a Code coverage collector for each programanalysis.

Z Open Unit Test Host Utilities provides the ccstart script to start a Codecoverage collector which remains active. This collector can then be used in multipleCode coverage invocations. The ccstop script can be used to stop the collector.


These scripts (ccstart, ccstop, and codecov) are located in /usr/lpp/IBM/idzutil/bin/ if you installed Z Open Unit Test Host Utilities in the default location. Forusage of these scripts, see Running code coverage in headless mode by using adaemon in the IBM Z Open Unit Test Knowledge Center.

The following is a generic usage scenario:1. Invoke ccstart with option to use a fixed port number and option to redirect

the output to a known location.2. Invoke, as often as needed, programs to be analyzed with startup

option.TEST(,,,TCPIP&<hostip>:<port>).3. Invoke ccstop.4. Direct the Z Open Unit Test client to the output location to see the reports.

Code coverage outputThe output of code coverage is intended to be imported into a Z Open Unit Testclient, and is therefore written to a z/OS UNIX file. Code coverage is also able touse the results of a previous run and combine them with the results of the currentrun, resulting in a single report that covers multiple code paths.

For these reasons, Z Open Unit Test Host Utilities does not attempt to remove theoutput of a code coverage run, and the output will thus accumulate over time.

z/OS UNIX provides a shell script, skulker, that deletes files based on thedirectory they are in and their age. Combined with the z/OS UNIX cron daemon,which runs commands at specified dates and times, you can set up an automatedtool that periodically cleans out targeted directories. Refer to UNIX System ServicesCommand Reference (SA22-7802) for more information about the skulker script andthe cron daemon.

Chapter 3. Host-based code analysis 25

Chapter 4. Other customization tasks

This section combines various optional customization tasks. To configure therequired service, follow the instructions in the appropriate section.

Z Open Unit Test related customizations to or for other products:v “z/OS UNIX subprojects”v “Include preprocessor support” on page 28v “xUnit support for Enterprise COBOL and PL/I” on page 28v “xUnit support for CICS applications” on page 30

z/OS UNIX subprojects

This customization task does not require assistance, special resources, or specialcustomization tasks.

REXEC (Remote Execution) is a TCP/IP service that enables clients to execute acommand on the host system. SSH (Secure Shell) is a similar service, but allcommunication is encrypted. Z Open Unit Test uses either service for doing remote(host-based) actions in z/OS UNIX subprojects.

Notes:

v Z Open Unit Test uses the z/OS UNIX version of REXEC, not the TSO version.v If REXEC/SSH is not configured to use the default port, the Z Open Unit Test

client must define the correct port for use by z/OS UNIX subprojects. Thisconfiguration can be done by selecting Window > Preferences > z/OS Solutions> USS Subprojects > Remote Action Options preference page. To know whichport is used, see “REXEC or SSH setup.”

REXEC or SSH setupREXEC and SSH rely on services provided by INETD (Internet Daemon), which isanother TCP/IP service. Communications Server IP Configuration Guide (SC31-8775)describes the steps required to set up INETD, REXEC, and SSH.

A common port used by REXEC is 512. To verify the port being used, check/etc/inetd.conf and /etc/services.v Find the service name (1st word, exec in this example) of the rexecd server (7th

word) in /etc/inetd.conf.exec stream tcp nowait OMVSKERN /usr/sbin/orexecd rexecd –LV

v Find the port (2nd word, 512 in this example) attached to this service name (1stword) in /etc/services.exec 512/tcp #REXEC Command Server

The same principle applies to SSH. Its common port is 22, and the server name issshd.


Include preprocessor support

This customization task does not require assistance, special resources, or specialcustomization tasks.

Z Open Unit Test supports the interpreting and expanding COBOL and PL/Iinclude statements, including select third-party include statements. Z Open UnitTest also provides a sample REXX exec, FEKRNPLI, that can be called by the Z OpenUnit Test client to expand PL/I source by invoking the PL/I compiler.

FEKRNPLI is located in FEL.#CUST.CNTL, unless you specified a different locationwhen you customized and submitted the FEL.SFELSAMP(FELSETUP) job. For moredetails, see Chapter 2, “Basic customization,” on page 13.

Customize the sample FEL.#CUST.CNTL(FEKRNPLI) exec, as described within themember. You must provide the following information:v compiler_hlq: The high-level qualifier for the PL/I compiler

The Z Open Unit Test client uses the TSO Command Service to execute the exec.This implies that if the FEKRNPLI exec is placed in the SYSPROC or SYSEXECconcatenation for the TSO Command Service, the user does not need to know theexact location of the exec. The user only needs to know the name. When using theLegacy ISPF Gateway, the SYSPROC or SYSEXEC concatenation is defined inISPF.conf. Customization of this file is documented in IBM Explorer for z/OS HostConfiguration Guide.

xUnit support for Enterprise COBOL and PL/I

This customization task does not require assistance, but does require the following resourcesor special customization tasks:

v PROCLIB update

v LINKLIST update

Frameworks that assist developers in writing code to perform repeatable,self-checking unit tests are collectively known as xUnit. Z Open Unit Test providessuch a framework for unit testing of Enterprise COBOL and PL/I code, calledzUnit.

To use the zUnit framework, developers need access to the AZU* and IAZU* loadmodules in the FEL.SFELLOAD load library, either through STEPLIB or LINKLIST.The zUnit test runner, AZUTSTRN, in turn needs access to various system libraries,either through STEPLIB or LINKLIST:v CEE.SCEERUN and CEE.SCEERUN2 (LE runtime)v SYS1.CSSLIB (callable system services)v SYS1.SIXMLOD1 (XML toolkit)

The zUnit test runner also needs access to a load library that holds the differenttest cases. This library is likely to be unique to a developer.


The zUnit test runner, AZUTSTRN, can be called by the Z Open Unit Test client inbatch mode, from the TSO command line, and from the z/OS UNIX commandline. When called in batch mode, the zUnit test runner can be used to unit testprograms that interact with DB2.v Z Open Unit Test provides sample procedures, AZUZUNIT and AZUZUDB2, to

simplify the calling of the zUnit test runner in batch mode. The sampleprocedures are located in FEL.#CUST.PROCLIB, unless you specified a differentlocation when you customized and submitted the FEL.SFELSAMP(FELSETUP) job.For more details, see “Customization setup” on page 13.Customize the sample procedures, as described within the member, and copythem to SYS1.PROCLIB.The name of the procedure and the names of the steps in the procedure matchthe default properties that are included with the Z Open Unit Test client. If thename of a procedure or the name of a step in a procedure is changed, thecorresponding properties file on all of the clients must be updated. You shouldnot change the procedure and step names.If the procedures cannot be copied into a system procedure library, ask the ZOpen Unit Test users to add a JCLLIB card right after the JOB card to theircalling job.//MYJOB JOB <job parameters>//PROCS JCLLIB ORDER=(FEL.#CUST.PROCLIB)

v For calling the zUnit test runner from z/OS UNIX (using the/usr/lpp/IBM/idz/bin/zunit script), you can specify the required non-LINKLISTdata sets in the STEPLIB directive of idz.env, thus simplifying the setup for thedeveloper.idz.env is located in /etc/zexpl/, unless you specified a different location whenyou customized and submitted FEL.SFELSAMP(FELSETUP) job. For more details,see “Customization setup” on page 13. You can edit the file with the TSO OEDITcommand.The zunit script allows the user to specify data sets that will be added to theSTEPLIB directive used by the script.

v For calling the zUnit test runner from the TSO command line by using theFEL.SFELPROC(FEKZUNIT) exec, the system libraries must exist in LINKLIST. Ifthey do not, developers must specify the system data set names on every callinstance of the zUnit test runner. You can also write a wrapper exec that doesthe TSOLIB allocations of these data sets for them. You can use FEKZUNIT itselfas an example of how to code this wrapper exec.

v To start a debugger session at the test target source, EQAOPTS load moduleshould be built and located in system search path like STEPLIB.

Note: EQAOPTS load module data set needs to be put before the DTSEQAMOD data set in the search path. It should contain the following macro sothat zUnit would specify the name of target source:EQAXOPT DLAYDBG,YESEQAXOPT DLAYDBGDSN,’&&USERID.ZUNIT.DLAYDBG.EQAUOPTS

The zUnit test runner allows for automatic reformatting of test reports. Z OpenUnit Test provides sample conversions (for example, conversion to Ant or jUnitformat), which are located in /usr/lpp/IBM/idz/samples/zunit/xsd and/usr/lpp/IBM/idz/samples/zunit/xsl, if you installed Z Open Unit Test in thedefault /usr/lpp/IBM/idz location.

Chapter 4. Other customization tasks 29

xUnit support for CICS applicationsYou need the assistance of a CICS and TCP/IP administrator to complete thiscustomization task, which requires specific resources or special customizationtasks.v Update CICS region JCLv Define resources to CICSv Reserve a TCP/IP port

Frameworks that assist developers in writing code to perform repeatable,self-checking unit tests are collectively known as xUnit. IBM Z Open Unit Testprovides such a framework for unit testing of Enterprise COBOL and PL/I code,called z/OS Automated Unit Testing Framework (zUnit). This customization taskextends zUnit to support testing CICS applications through recording of theparameters used in EXEC CICS calls.

To record a CICS application, zUnit requires the following CICS updates:v CICS system initialization (SIT) parameter updates

– Specify TCPIP=YES.– Specify USSHOME=/usr/lpp/cicsts/cicsts54, where /usr/lpp/cicsts/cicsts54

is the path where CICS is installed.v CICS JCL updates:

– Specify REGION=0M on the EXEC statement to provide sufficient room to bufferthe recording.

– Define the FEL.SFELLOAD load library in the region’s DFHRPL DD statement,where FEL is the high level qualifier used during the SMP/E install of Z OpenUnit Test.

v CICS CSD updates:Define zUnit to your CICS region, as documented in the AZUCSD sample CSDupdate job. AZUCSD is located in FEL.#CUST.JCL, unless you specified adifferent location when you customized and submitted jobFEL.SFELSAMP(FELSETUP). For more information. see “Customization setup”on page 13.

The zUnit CICS recording service uses a CICS PIPELINE to communicate with thezUnit client. This CICS service requires that a TCP/IP port be defined in the CSD.The developers who use this service need to know the host system name and theport on which the service is listening.

Note: Note: The zUnit CICS recording service uses auxiliary TS queue spaces tostore log data and temporarily cache the recorded data. The log data is written to aqueue named _AZU_LOG_. You can browse the log data with the CICS commandCEBR. When the log data is too big to reserve auxiliary TS queue spaces for otherprograms,purge it manually in the CEBR command screen. Abend AIER (resp-18NOSPACE) occurs when an auxiliary TS queue runs out of space.


Chapter 5. Security definitions

Customize and submit the sample FELRACF job, which has sample RACFcommands to create the basic security definitions for Z Open Unit Test.

FELRACF is located in FEL.#CUST.JCL, unless you specified a different location whenyou customized and submitted the FEL.SFELSAMP(FELSETUP) job.

See the RACF Command Language Reference (SA22–7687) for more information aboutRACF commands.

Requirements and checklistTo complete the security setup, the security administrator must know the valuesthat are listed in Table 11. These values were defined during previous steps of theinstallation and customization of Z Open Unit Test.

Table 11. Security setup variables

Description

v Default value

v Where to find the answer Value

Z Open Unit Test producthigh-level qualifier

v FEL

v SMP/E installation

Z Open Unit Testcustomization high-levelqualifier

v FEL.#CUST

v FEL.SFELSAMP(FELSETUP),as described in“Customization setup” onpage 13.

The following list is an overview of the actions that are required to complete thebasic security setup of Z Open Unit Test. As documented in the following sections,different methods can be used to fulfill these requirements, depending on therequired security level.v “Define the data set profiles”v “Verify the security settings” on page 32

Define the data set profilesREAD access for users and ALTER for system programmers is sufficient for most ZOpen Unit Test data sets. Replace the #sysprog placeholder with valid user IDs orRACF group names. Also, ask the system programmer who installed andconfigured the product for the correct data set names. FEL is the default high-levelqualifier used during installation and FEL.#CUST is the default high-level qualifierfor data sets created during the customization process.v

ADDGROUP (FEL) OWNER(IBMUSER) SUPGROUP(SYS1)DATA(’IBM Z Open Unit Test - HLQ STUB’)

vADDSD ’FEL.*.**’ UACC(READ)DATA(’IBM Z Open Unit Test’)


vPERMIT ’FEL.*.**’ CLASS(DATASET) ACCESS(ALTER) ID(#sysprog)

vSETROPTS GENERIC(DATASET) REFRESH

Notes:

v Protect FEL.SFELLPA against updates because this data set is loaded into LPA,which is APF authorized by default.

v The sample commands in this publication and in the FELRACF job assume thatEnhanced Generic Naming (EGN) is active. When EGN is active, the ** qualifiercan be used to represent any number of qualifiers in the DATASET class.Substitute ** with * if EGN is not active on your system. For more informationabout EGN, see Security Server RACF Security Administrator's Guide (SA22-7683).

Verify the security settingsUse the following sample commands to display the results of your security-relatedcustomizations.v Data set profiles

– LISTGRP FEL

– LISTDSD PREFIX(FEL) ALL


Chapter 6. Migration guide

Migration considerationsThis section highlights installation and configuration changes compared toprevious releases of the product. It also gives some general guidelines to migrateto this release. For more information, see the related sections in this manual.v If you are a previous user of IBM Z Open Unit Test, save the related customized

files before upgrading to this version of IBM Z Open Unit Test.v If you plan on running multiple instances of Z Open Unit Test, read "Running

multiple instances" in the IBM Explorer for z/OS Host Configuration Reference.v If your migration scenario spans more than two releases, you should do the

customizations again, as if there is no older release present.

Backing up the previously configured filesIf you are a previous user of Z Open Unit Test, save the related customized filesbefore installing this version of IBM Z Open Unit Test.

Customizable Z Open Unit Test files can be found at the following locations:v Version 1.0 and later

– FEL.SFELSAMP, some members are copied to FEL.#CUST.* by the FELSETUPsample job, where * equals PARMLIB, PROCLIB, JCL, CNTL, ASM and SQL

– /usr/lpp/IBM/idz/samples/, some files are copied to /etc/zexpl/ and/var/idz/sclmdt/* by the FELSETUP sample job, where * equals CONFIG/,CONFIG/PROJECT/ and CONFIG/script/

Migrate to version 1.0There are no migration actions for this first release of IBM Z Open Unit Test.


Notices

This information was developed for products and services offered in the US. Thismaterial might be available from IBM in other languages. However, you may berequired to own a copy of the product or product version in that language in orderto access it.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement maynot apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided forconvenience only and do not in any manner serve as an endorsement of those


websites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

The performance data and client examples cited are presented for illustrativepurposes only. Actual performance results may vary depending on specificconfigurations and operating conditions.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBMproducts.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

Statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to actual people or business enterprises is entirelycoincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sample


programs are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Programming interface information

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational 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 andtrademark information" at www.ibm.com/legal/copytrade.shtml.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the followingterms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBMwebsite.

Personal use

You may reproduce these publications for your personal, noncommercial useprovided that all proprietary notices are preserved. You may not distribute, displayor make derivative work of these publications, or any portion thereof, without theexpress consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within yourenterprise provided that all proprietary notices are preserved. You may not makederivative works of these publications, or reproduce, distribute or display thesepublications or any portion thereof outside your enterprise, without the expressconsent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses orrights are granted, either express or implied, to the publications or anyinformation, data, software or other intellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in itsdiscretion, the use of the publications is detrimental to its interest or, asdetermined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in fullcompliance with all applicable laws and regulations, including all United Statesexport laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESEPUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING

Notices 37

http://www.ibm.com/legal/us/en/copytrade.shtml

BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY,NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.


Readers’ Comments — We'd Like to Hear from You

IBM Z Open Unit TestVersion 1.0Host Configuration Guide

Publication No. SC27-9413-00

We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,organization, subject matter, or completeness of this book. The comments you send should pertain to only theinformation in this manual or product and the way in which the information is presented.

For technical questions and information about products and prices, please contact your IBM branch office, yourIBM business partner, or your authorized remarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in anyway it believes appropriate without incurring any obligation to you. IBM or any other organizations will only usethe personal information that you supply to contact you about the issues that you state on this form.

Comments:

Thank you for your support.

Send your comments to the address on the reverse side of this form.

If you would like a response from IBM, please fill in the following information:

Name Address

Company or Organization

Phone No. Email address

Readers’ Comments — We'd Like to Hear from YouSC27-9413-00

SC27-9413-00

IBM®Cut or FoldAlong Line

Cut or FoldAlong Line

Fold and Tape Please do not staple Fold and Tape

Fold and Tape Please do not staple Fold and Tape

NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES

BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

IBM CorporationBuilding 501P.O Box 12195Research Triangle Park, NCUSA 27709-2195

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

_

IBM®

Printed in USA

SC27-9413-00

ibm z open unit test version 1.0: host configuration guide€¦ · open unit t est host system r...

Documents