Program Directory for IBM Rational DOORS Next Generation

Transcription

1 IBM Program Directory for IBM ational DOOS Next Generation V Program Number 5724-W87 for Use with z/os Document Date: June 2017 GI

2 Note Before using this information and the product it supports, be sure to read the general information under 7.0, Notices on page 44. opyright International Business Machines orporation 2008, US Government Users estricted ights Use, duplication or disclosure restricted by GSA ADP Schedule ontract with IBM orp.

3 ontents 1.0 Introduction ational DOOS Next Generation Description ational DOOS Next Generation FMIDs Program Materials Basic Machine-eadable Material Optional Machine-eadable Material Program Publications Optional Program Publications Program Source Materials Publications Useful During Installation Program Support Program Services Preventive Service Planning Statement of Support Procedures Program and Service evel Information Program evel Information Service evel Information Installation equirements and onsiderations Driving System equirements Machine equirements Programming equirements Target System equirements Machine equirements Programming equirements Installation equisites Operational equisites Toleration/oexistence equisites Incompatibility (Negative) equisites DASD Storage equirements FMIDs Deleted Special onsiderations Installation Instructions Installing ational DOOS Next Generation SMP/ onsiderations for Installing ational DOOS Next Generation SMP/ Options Subentry Values Overview of the installation steps Upload Sample J from the client opyright IBM orp. 2008, 2017 iii

4 6.1.5 xpand the sample jcl file by using the TSO eceive command: Sample Jobs un the job to allocate sequential data sets that the FTP step will use Upload the compressed FIS and SMPMS from the client xpand the FIs by running the sample job, BZXPND: Delete previous release of ational DOOS Next Generation (Optional) Allocate SMP/ SI (Optional) Perform SMP/ IV Allocate SMP/ Target and Distribution ibraries Allocate, create and mount ZFS File System (Optional) Allocate File System Paths reate DDDF ntries Perform SMP/ APPY Perform SMP/ APT un POT OSSZON Activating ational DOOS Next Generation Product ustomization Notices Trademarks eader's omments Figures 1. Program File ontent for HJS604 - ational Jazz Team Server Program File ontent for HBT604 - Build System Toolkit Program File ontent for HDV604 - ational Developer for z System subset Program File ontent for HBA604 - ational Build Agent Program File ontent for HM604 - hange and onfiguration Management Program File ontent for HQM604 - Quality Management Program File ontent for HM604 - equirements Management Program File ontent for H604 - ational ommon omponents Program File ontent for HW604 - ational Websphere iberty Program File ontent for HS604 - IBM Jazz eporting Services Program File ontent for HG604 - ational Global onfiguration Management Program File ontent for H604 - ational ngineering ifecycle Manager Program File ontent for HI604 - ational ink Index Provider Publications Useful During Installation PSP Upgrade and Subset ID omponent IDs Driving System Software equirements iv ational DOOS Next Generation Program Directory

5 18. Total DASD Space equired by ational DOOS Next Generation Storage equirements for ational DOOS Next Generation Target ibraries ational DOOS Next Generation File System Paths Storage equirements for ational DOOS Next Generation Distribution ibraries Storage equirements for ational DOOS Next Generation - Additional Installation Data Sets SMP/ Options Subentry Values User ntered Values Sample Installation Jobs Figures v

6 vi ational DOOS Next Generation Program Directory

7 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 ational DOOS Next Generation. This publication refers to IBM ational DOOS Next Generation as ational DOOS Next Generation. The Program Directory contains the following sections: 2.0, Program Materials on page 4 identifies the basic program materials and documentation for ational DOOS Next Generation. 3.0, Program Support on page 10 describes the IBM support available for ational DOOS Next Generation. 4.0, Program and Service evel Information on page 13 lists the APAs (program level) and PTFs (service level) that have been incorporated into ational DOOS Next Generation. 5.0, Installation equirements and onsiderations on page 14 identifies the resources and considerations that are required for installing and using ational DOOS Next Generation. 6.0, Installation Instructions on page 24 provides detailed installation instructions for ational DOOS Next Generation. It also describes the procedures for activating the functions of ational DOOS Next Generation, or refers to appropriate publications. 1.1 ational DOOS Next Generation Description With this release, ational equirements omposer is renamed to IBM ational DOOS Next Generation. IBM ational DOOS Next Generation 5.0 helps teams achieve a better development outcome through improved requirements definition and management. Performance and scale In order to reduce the functional load on the Jazz Team Server (JTS) and to support more flexible deployment options this release enhances the overall architecture by moving the M specific data on to the M server. In previous releases the architecture for ational DOOS Next Generation has differed from other M applications in that all data was stored within the central Jazz Team Server and this is now made consistent. Support for multiple M application servers sharing a single JTS is now possible utilizing the new data architecture. A single JTS ensures that users, licenses and other central configurations can be shared over multiple M deployments while gaining the advantage of higher data scale by segregating different programs into their own M servers. A data migration is therefore required for this release to move the M data to the M server and to rerun the indexes for the data in this new location. Instructions can be found in the installation guide opyright IBM orp. 2008,

8 and extended configuration guidelines detailing hardware and configuration guidelines can be found on our Jazz.net pages. Usability nd user productivity improvements: improving both the speed in which end users are able to perform their tasks and enhancing the look of the overall environment in which they work. Major module editing improvements to focus on end user productivity. Improvements over the last 12 months have included: Seamless and quick keyboard shortcuts avoiding the need to switch from keyboard to mouse on a frequent basis asier editing of individual requirements View and modify artifact properties from within the module user interface Preferred requirement types accelerating accurate module production Huge performance improvements in editing and scrolling modules or larger sizes (10k+) Display and manipulate folder hierarchy while browsing module data Drag and drop enabled throughout the user interface allowing move and copy of artifacts, restructure within modules and linking between different modules in different web browser tabs or windows Metric reporting both built into the tool and support for custom reports complying with organization process guidelines Delivered through a web only user interface DOOS Next Generation provides all capabilities deployable in a cost effective way Integrations and extensions with OS and JavaScript JavaScript extensions: ational DOOS Next Generation introduced the facility of using JavaScript to provide extensions to the product. This new release offers further capability for interacting with requirements data to offer stronger utilities: - reation, deletion and move of requirements within a module - equirement (artifact) type manipulation - Access to user details to allow script extensions to self moderate themselves - A new example script has been provided to demonstrate how to use the new facilities to convert a flat module into a module containing hierarchy. This is an excellent example of using JavaScript to help manipulate imported data from SV files OS and Web services: The OS API has been extended to allow the creation of M specific link types through API calls. 2 ational DOOS Next Generation Program Directory

9 Non-functional requirements The following platforms are now supported by ational DOOS Next Generation: MS SQ Server 2012 Microsoft Windows 8.1 Microsoft Internet xplorer 11 hrome 30 Note: The following platforms are no longer supported by ational DOOS Next Generation: Microsoft Windows XP Microsoft Windows Vista Microsoft Internet xplorer ational DOOS Next Generation FMIDs ational DOOS Next Generation consists of the following FMIDs: HJS604 - ational Jazz Team Server HBT604 - ational Team oncert - Build System Toolkit HDV604 - ational Team oncert - ational Developer for z System subset HBA604 - ational Build Agent HM604 - ational Team oncert - hange and onfiguration Management (M) HQM604 - ational Quality Manager - Quality Management (QM) HM604 - ational DOOS Next Generation - equirements Management (M) H604 - ational ommon omponents HW604 - ational Websphere iberty HS604 - IBM Jazz eporting Services HG604 - ational Global onfiguration Management H604 - ational ngineering ifecycle Manager HI604 - ational ink Index Provider Note! 1. FMID H604 (ational ommon omponents) is required by the other FMIDS. If you are installing IBM ational DOOS Next Generation for the first time, you must install FMID H604. If you have previously installed FMID H604, there is no need to re-install it. Introduction 3

10 2.0 Program Materials An IBM program is identified by a program number. The program number for ational DOOS Next Generation is 5724-W87. Basic Machine-eadable 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 ational DOOS Next Generation. Ask your IBM representative for this information if you have not already received a copy. 2.1 Basic Machine-eadable Material The distribution medium for this program is DVD. It is installed using SMP/, and is in SMP/ FI format. See 6.0, Installation Instructions on page 24 for more information about how to install the program. Figure 1 describes the program file content for ational DOOS Next Generation. Notes: 1. The data set attributes in this table must be used in the J of jobs that read the data sets. However, because the data sets are in IBOPY unloaded format, their actual attributes might be different. 2. If any FIs are identified as PDSs, ensure that SMPTIB data sets are allocated as PDSs. Figure 1. Program File ontent for HJS604 - ational Jazz Team Server Name SMPMS SQ FB IBM.HJS604.F1 PDS FB O G F M BK SIZ IBM.HJS604.F2 PDS VB opyright IBM orp. 2008, 2017

11 Figure 2. Program File ontent for HBT604 - Build System Toolkit Name SMPMS SQ FB IBM.HBT604.F1 PDS FB O G F M BK SIZ IBM.HBT604.F2 PDS VB IBM.HBT604.F3 PDS FB IBM.HBT604.F4 PDS FB IBM.HBT604.F5 PDS FB IBM.HBT604.F6 PDS FB IBM.HBT604.F7 PDS FB IBM.HBT604.F8 PDS FB IBM.HBT604.F9 PDS FB IBM.HBT604.F10 PDS U Figure 3. Program File ontent for HDV604 - ational Developer for z System subset Name SMPMS SQ FB IBM.HDV604.F1 PDS U IBM.HDV604.F2 PDS FB IBM.HDV604.F3 PDS U O G F M BK SIZ Figure 4. Program File ontent for HBA604 - ational Build Agent Name SMPMS SQ FB IBM.HBA604.F1 PDS FB O G F M BK SIZ IBM.HBA604.F2 PDS VB Program Materials 5

12 Figure 5. Program File ontent for HM604 - hange and onfiguration Management Name SMPMS SQ FB IBM.HM604.F1 PDS FB O G F M BK SIZ IBM.HM604.F2 PDS VB Figure 6. Program File ontent for HQM604 - Quality Management Name SMPMS SQ FB IBM.HQM604.F1 PDS FB O G F M BK SIZ IBM.HQM604.F2 PDS VB Figure 7. Program File ontent for HM604 - equirements Management Name SMPMS SQ FB IBM.HM604.F1 PDS FB O G F M BK SIZ IBM.HM604.F2 PDS VB ational DOOS Next Generation Program Directory

13 Figure 8. Program File ontent for H604 - ational ommon omponents Name SMPMS SQ FB IBM.H604.F1 PDS FB IBM.H604.F2 PDS FB O G F M BK SIZ IBM.H604.F3 PDS VB IBM.H604.F4 PDS U IBM.H604.F5 PDS FB IBM.H604.F6 PDS FB IBM.H604.F7 PDS FB IBM.H604.F8 PDS FB IBM.H604.F9 PDS FB IBM.H604.F10 PDS FB IBM.H604.F11 PDS FB IBM.H604.F12 PDS FB IBM.H604.F13 PDS FB IBM.H604.F14 PDS FB Figure 9. Program File ontent for HW604 - ational Websphere iberty Name SMPMS SQ FB IBM.HW604.F1 PDS FB O G F M BK SIZ IBM.HW604.F2 PDS VB Program Materials 7

14 Figure 10. Program File ontent for HS604 - IBM Jazz eporting Services Name SMPMS SQ FB IBM.HS604.F1 PDS FB O G F M BK SIZ IBM.HS604.F2 PDS VB Figure 11. Program File ontent for HG604 - ational Global onfiguration Management Name SMPMS SQ FB IBM.HG604.F1 PDS FB O G F M BK SIZ IBM.HG604.F2 PDS VB Figure 12. Program File ontent for H604 - ational ngineering ifecycle Manager Name SMPMS SQ FB IBM.H604.F1 PDS FB O G F M BK SIZ IBM.H604.F2 PDS VB Figure 13. Program File ontent for HI604 - ational ink Index Provider Name SMPMS SQ FB IBM.HI604.F1 PDS FB O G F M BK SIZ IBM.HI604.F2 PDS VB ational DOOS Next Generation Program Directory

15 2.2 Optional Machine-eadable Material No optional machine-readable materials are provided for ational DOOS Next Generation. 2.3 Program Publications The following sections identify the basic publications for ational DOOS Next Generation Optional Program Publications No optional publications are provided for ational DOOS Next Generation. 2.4 Program Source Materials No program source materials or viewable program listings are provided for ational DOOS Next Generation. 2.5 Publications Useful During Installation You might want to use the publications listed in Figure 14 during the installation of ational DOOS Next Generation. Figure 14. Publications Useful During Installation Publication Title Form Number Media Format IBM SMP/ for z/os User's Guide SA IBM SMP/ for z/os ommands SA IBM SMP/ for z/os eference SA IBM SMP/ for z/os Messages, odes, and Diagnosis GA Program Materials 9

16 3.0 Program Support This section describes the IBM support available for ational DOOS Next Generation. 3.1 Program Services ontact your IBM representative for specific information about available program services. 3.2 Preventive Service Planning Before you install ational DOOS Next Generation, make sure that you have reviewed the current Preventive Service Planning (PSP) information. eview the PSP Bucket for General Information, Installation Documentation, and the ross Product Dependencies sections. For the ecommended Service section, instead of reviewing the PSP Bucket, it is recommended you use the IBM.ProductInstall-equiredService fix category in SMP/ to ensure you have all the recommended service installed. Use the FIXAT(IBM.ProductInstall-equiredService) operand on the APPY HK command. See , Perform SMP/ APPY on page 40 for a sample APPY command. Once you have received your installation DVD, you should contact the IBM Support enter or use S/390 SoftwareXcel to obtain the latest PSP Bucket information. You can also obtain the latest PSP Bucket information by going to the following Web site: You can also use S/390 SoftwareXcel or contact the IBM Support enter to obtain the latest PSP Bucket information. For program support, access the Software Support Website at PSP Buckets are identified by UPGADs, which specify product levels; and SUBSTs, which specify the FMIDs for a product level. The UPGAD and SUBST values for ational DOOS Next Generation are included in Figure 15. Figure 15 (Page 1 of 2). PSP Upgrade and Subset ID UPGAD SUBST Description 5724V82 HJS604 ational Jazz Team Server for z/os HBT604 HDV604 HBA604 ational Team oncert - Build System Toolkit for z/os ational Team oncert - ational Developer for z System subset ational Build Agent for z/os 10 opyright IBM orp. 2008, 2017

17 Figure 15 (Page 2 of 2). PSP Upgrade and Subset ID UPGAD SUBST Description HM604 ational Team oncert - hange and onfiguration Management for z/os HQM604 HM604 H604 HW604 HS604 HG604 H604 HI604 ational Quality Manager - Quality Management for z/os ational DOOS Next Generation - equirements Management for z/os ational ommon omponents for z/os ational Websphere iberty for z/os IBM Jazz eporting Services for z/os ational Global onfiguration Management for z/os ational ngineering ifecycle Manager for z/os ational ink Index Provider for z/os 3.3 Statement of Support Procedures eport any problems which you feel might be an error in the product materials to your IBM Support enter. You may be asked to gather and submit additional diagnostics to assist the IBM Support enter in their analysis. Figure 16 identifies the component IDs (OMPID) for ational DOOS Next Generation. Figure 16 (Page 1 of 2). omponent IDs FMID OMPID omponent Name HJS V8210 ational Jazz Team Server for z/os 604 HBT V8220 ational Team oncert - Build System Toolkit for z/os 604 HDV V8230 ational Team oncert - ational Developer for z System subset HBA V8240 ational Build Agent for z/os 604 HM V8260 ational Team oncert - hange and onfiguration Management for z/os HQM V8270 ational Quality Manager - Quality Management for z/os 604 HM V8280 ational DOOS Next Generation - equirements Management for z/os H V82 ational ommon omponents for z/os 604 HW V82W ational Websphere iberty for z/os 604 TAIN elease Program Support 11

18 Figure 16 (Page 2 of 2). omponent IDs FMID OMPID omponent Name HS V82J IBM Jazz eporting Services for z/os 604 HG V82G ational Global onfiguration Management for z/os 604 H V82M ational ngineering ifecycle Manager for z/os 604 HI V82I ational ink Index Provider for z/os 604 TAIN elease 12 ational DOOS Next Generation Program Directory

19 4.0 Program and Service evel Information This section identifies the program and relevant service levels of ational DOOS Next Generation. The program level refers to the APA 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 evel Information No APAs have been incorporated into ational DOOS Next Generation. 4.2 Service evel Information No PTFs against this release of ational DOOS Next Generation have been incorporated into the product package. Frequently check the ational DOOS Next Generation PSP Bucket for HIP and SPIA attention PTFs against all FMIDs that you must install. You can also receive the latest HODDATA, then add the FIXAT(IBM.PODUTINSTA-QUIDSVI) operand on your APPY HK command. This will allow you to review the recommended and critical service that should be installed with your FMIDs. opyright IBM orp. 2008,

20 5.0 Installation equirements and onsiderations The following sections identify the system requirements for installing and activating ational DOOS Next Generation. The following terminology is used: Driving system: the system on which SMP/ 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 IP-able clone of the running system to use as a target system. The clone must include copies of all system libraries that SMP/ updates, copies of the SMP/ SI data sets that describe the system libraries, and your PAMIB and POIB. 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 equirements This section describes the environment of the driving system required to install ational DOOS Next Generation Machine equirements The driving system can run in any hardware environment that supports the required software Programming equirements 14 opyright IBM orp. 2008, 2017

21 Figure 17. Driving System Software equirements Program Number Product Name Minimum VM Minimum Service evel will satisfy these APAs 5650-ZOS z/os V or higher N/A No Included in the shipped product? Note: SMP/ is a requirement for Installation and is an element of z/os but can also be ordered as a separate product, 5655-G44, minimally V Note: Installation might require migration to new z/os releases to be service supported. See Target System equirements This section describes the environment of the target system required to install and use ational DOOS Next Generation. ational DOOS Next Generation installs in the z/os (Z038) S Machine equirements The target system can run in any hardware environment that supports the required software Programming equirements Installation equisites: 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. ational DOOS Next Generation has no mandatory installation requisites. onditional 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. ational DOOS Next Generation has no conditional installation requisites. Installation equirements and onsiderations 15

22 Operational equisites: 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 part of its functions. Mandatory operational requisites identify products that are required for this product to operate its basic functions. ational DOOS Next Generation has no mandatory operational requisites. onditional 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. ational DOOS Next Generation has no conditional operational requisites Toleration/oexistence equisites: Toleration/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. ational DOOS Next Generation has no toleration/coexistence requisites Incompatibility (Negative) equisites: Negative requisites identify products that must not be installed on the same system as this product. ational DOOS Next Generation has no negative requisites DASD Storage equirements ational DOOS Next Generation libraries can reside on all supported DASD types. Figure 18 lists the total space that is required for each type of library. Figure 18. Total DASD Space equired by ational DOOS Next Generation ibrary Type ompressed Binaries xpanded Installation Files Target Distribution File System(s) HFS or zfs * Total Space equired in 3390 Trks Tracks Tracks 412 Tracks Tracks Tracks 16 ational DOOS Next Generation Program Directory

23 * Note regarding HFS/zFS space allocation For the HFS/zFS allocation the total number of tracks of is specified. However, if only certain FMIDs are going to be applied your HFS/zFS space allocation can be reduced. The following lists the HFS/zFS allocation per FMID to enable you to size your HFS/zFS accordingly. HJS Tracks HBT Tracks HBA Tracks HM Tracks HQM Tracks HM Tracks H Tracks HW Tracks HS Tracks HG Tracks H Tracks HI Tracks Notes: 1. For non-fm U data sets, IBM recommends using system-determined block sizes for efficient DASD utilization. For FM 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 S Unique data set, allocated by this product and used by only 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. 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 exists, it must have enough free space to accommodate the storage size given in this table. xisting 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. If you currently have a previous release of this product installed in these libraries, the installation of this release will delete the old release and reclaim the space that was used by the old release and any service that had been installed. You can determine whether these libraries have enough space by deleting the old release with a dummy function, compressing the libraries, and comparing the space requirements with the free space in the libraries. For more information about the names and sizes of the required data sets, see , Allocate SMP/ Target and Distribution ibraries on page 38. Installation equirements and onsiderations 17

24 3. Abbreviations used for the file system path type are as follows. N X P New path, created by this product. Path created by this product, but might already exist from a previous release. 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 can be either a PDS or a PDS, except SBZAUTH, ABZAUTH and ABZHFS which must be PDSs. 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 IP volume. The values in the "Member Type" column are not necessarily the actual SMP/ element types that are identified in the SMPMS. 6. All target libraries that are listed and contain load modules have the following attributes: These data sets can be in the PA, but they are not required to be in the PA. These data sets can be in the NKST. These data sets are not required to be APF-authorized, except for SBZAUTH. ational DOOS Next Generation requires that the SMPTS data set must be a PDS. If your existing SMPTS is a PDS, you will need to allocate a new PDS and copy your existing SMPTS into it and then change the SMPTS DDDF entry to indicate the new PDS data set. The following figures describe the target and distribution libraries and file system paths required to install ational DOOS Next Generation. The storage requirements of ational DOOS Next Generation must be added to the storage required by other programs that have data in the same library or path. Note: Use the data in these tables to determine which libraries can be merged into common data sets. In addition, since some AIAS names may not be unique, ensure that no naming conflicts will be introduced before merging libraries. Figure 19 (Page 1 of 2). Storage equirements for ational DOOS Next Generation Target ibraries ibrary DDNAM Member Type Target Volume T Y P O G F M No. of 3390 Trks SBZAUTH APF Modules ANY U PDS U 0 35 n/a SBZDBM DBM ANY U PDS FB SBZX X ANY U PDS FB SBZJ Install J ANY U PDS FB No. of DI Blks 18 ational DOOS Next Generation Program Directory

25 Figure 19 (Page 2 of 2). Storage equirements for ational DOOS Next Generation Target ibraries ibrary DDNAM Member Type Target Volume T Y P O G F M No. of 3390 Trks SBZOAD Modules ANY U PDS U SBZMNP Messages ANY U PDS FB SBZMNU Messages ANY U PDS FB SBZMJPN Messages ANY U PDS FB SBZPNP Panels ANY U PDS FB SBZPNU Panels ANY U PDS FB SBZPJPN Panels ANY U PDS FB SBZSAMP Samples ANY U PDS FB SBZSIB Skeletons ANY U PDS FB SBZTIB Table ANY U PDS FB No. of DI Blks Figure 20 (Page 1 of 2). ational DOOS Next Generation File System Paths DDNAM T Y P Path Name SBZA001 N /usr/lpp/jazz/v6.0.4/ibm/ SBZA002 N /usr/lpp/jazz/v6.0.4/server/conf/jts/provision_profiles/ibm/ SBZA003 N /usr/lpp/jazz/v6.0.4/server/conf/ccm/provision_profiles/ibm/ SBZA004 N /usr/lpp/jazz/v6.0.4/server/conf/qm/provision_profiles/ibm/ SBZA005 N /usr/lpp/jazz/v6.0.4/server/conf/rm/provision_profiles/ibm/ SBZA006 N /usr/lpp/jazz/v6.0.4/server/conf/dcc/provision_profiles/ibm/ SBZA007 N /usr/lpp/jazz/v6.0.4/server/conf/gc/provision_profiles/ibm/ SBZA008 N /usr/lpp/jazz/v6.0.4/server/conf/relm/provision_profiles/ibm/ SBZAD02 N /usr/lpp/jazz/v6.0.4/server/conf/jts/provision_profiles/ibm/ SBZAD03 N /usr/lpp/jazz/v6.0.4/server/conf/ccm/provision_profiles/ibm/ SBZAD04 N /usr/lpp/jazz/v6.0.4/server/conf/qm/provision_profiles/ibm/ SBZAD05 N /usr/lpp/jazz/v6.0.4/server/conf/rm/provision_profiles/ibm/ SBZAD06 N /usr/lpp/jazz/v6.0.4/server/conf/dcc/provision_profiles/ibm/ SBZAD07 N /usr/lpp/jazz/v6.0.4/server/conf/gc/provision_profiles/ibm/ Installation equirements and onsiderations 19

26 Figure 20 (Page 2 of 2). ational DOOS Next Generation File System Paths DDNAM T Y P Path Name SBZAD08 N /usr/lpp/jazz/v6.0.4/server/conf/relm/provision_profiles/ibm/ SBZ001 N /usr/lpp/jazz/v6.0.4/buildagent/ibm/ Figure 21. Storage equirements for ational DOOS Next Generation Distribution ibraries ibrary DDNAM T Y P O G F M No. of 3390 Trks ABZAUTH U PDS U 0 35 n/a ABZDBM U PDS FB ABZX U PDS FB ABZHFS * U PDS VB n/a ABZJ U PDS FB ABZOAD U PDS U ABZMNP U PDS FB ABZMNU U PDS FB ABZMJPN U PDS FB ABZPNP U PDS FB ABZPNU U PDS FB ABZPJPN U PDS FB ABZSAMP U PDS FB ABZSIB U PDS FB ABZTIB U PDS FB No. of DI Blks Note: * See , Allocate SMP/ Target and Distribution ibraries for more information of the size allocation of the ABZHFS data set. The following figures list additional data sets that are required for the installation of ational DOOS Next Generation. 20 ational DOOS Next Generation Program Directory

27 Figure 22 (Page 1 of 2). Storage equirements for ational DOOS Next Generation - Additional Installation Data Sets Data Set Name T Y P O G F M No. of 3390 Trks hlq.hjs604.f1.bin U PS FB n/a hlq.hjs604.f2.bin U PS FB n/a hlq.hbt604.f1.bin U PS FB n/a hlq.hbt604.f2.bin U PS FB n/a hlq.hbt604.f3.bin U PS FB 80 5 n/a hlq.hbt604.f4.bin U PS FB 80 5 n/a hlq.hbt604.f5.bin U PS FB n/a hlq.hbt604.f6.bin U PS FB 80 5 n/a hlq.hbt604.f7.bin U PS FB n/a hlq.hbt604.f8.bin U PS FB 80 5 n/a hlq.hbt604.f9.bin U PS FB n/a hlq.hbt604.f10.bin U PS FB n/a hlq.hdv604.f1.bin U PS FB n/a hlq.hdv604.f2.bin U PS FB 80 2 n/a hlq.hdv604.f3.bin U PS FB n/a hlq.hba604.f1.bin U PS FB 80 2 n/a hlq.hba604.f2.bin U PS FB n/a hlq.hm604.f1.bin U PS FB 80 5 n/a hlq.hm604.f2.bin U PS FB n/a hlq.hqm604.f1.bin U PS FB 80 5 n/a hlq.hqm604.f2.bin U PS FB n/a hlq.hm604.f1.bin U PS FB 80 5 n/a hlq.hm604.f2.bin U PS FB n/a hlq.h604.f1.bin U PS FB n/a hlq.h604.f2.bin U PS FB n/a hlq.h604.f3.bin U PS FB n/a hlq.h604.f4.bin U PS FB n/a hlq.h604.f5.bin U PS FB 80 4 n/a hlq.h604.f6.bin U PS FB 80 5 n/a No. of DI Blks Installation equirements and onsiderations 21

28 Figure 22 (Page 2 of 2). Storage equirements for ational DOOS Next Generation - Additional Installation Data Sets Data Set Name T Y P O G F M No. of 3390 Trks hlq.h604.f7.bin U PS FB 80 4 n/a hlq.h604.f8.bin U PS FB n/a hlq.h604.f9.bin U PS FB 80 4 n/a hlq.h604.f10.bin U PS FB n/a hlq.h604.f11.bin U PS FB 80 4 n/a hlq.h604.f12.bin U PS FB n/a hlq.h604.f13.bin U PS FB n/a hlq.h604.f14.bin U PS FB 80 2 n/a hlq.hw604.f1.bin U PS FB 80 3 n/a hlq.hw604.f2.bin U PS FB n/a hlq.hs604.f1.bin U PS FB 80 5 n/a hlq.hs604.f2.bin U PS FB n/a hlq.hg604.f1.bin U PS FB 80 5 n/a hlq.hg604.f2.bin U PS FB n/a hlq.h604.f1.bin U PS FB 80 5 n/a hlq.h604.f2.bin U PS FB n/a hlq.hi604.f1.bin U PS FB 80 5 n/a hlq.hi604.f2.bin U PS FB n/a No. of DI Blks 5.3 FMIDs Deleted Installing ational DOOS Next Generation into same SMP/ target and distribution libraries that contain a previous version of ational DOOS Next Generation might result in the deletion of other FMIDs. To see which FMIDs will be deleted, examine the ++V statement in the SMPMS of the product. If you do not want to delete these FMIDs at this time, install ational DOOS Next Generation into separate SMP/ target and distribution zones. If you want to delete these FMIDS it is recommended that you use a dummy function SYSMOD to delete the previous releases of ational DOOS Next Generation product from the existing target and distribution libraries, before proceeding with the installation of the new release. 22 ational DOOS Next Generation Program Directory

29 Note: These FMIDs are not automatically deleted from the Global Zone. If you want to delete these FMIDs from the Global Zone, use the SMP/ JT NOFMID DTFMID command. See the SMP/ ommands book for details. 5.4 Special onsiderations Security onsiderations: In ational DOOS Next Generation V , there are changes to the PassTicket support for the ISPF client. The necessary changes remove a redundant AF profile and add a new AF profile to increase the security in generating PassTickets. If you installed the ISPF client with a previous release, the following tasks should be performed: 1. emove the IPTAUTH.BZAPP.* profile, where BZAPP is the application ID used for the ISPF client. If you used a different application ID, the profile is named with the application ID you included in the profile name. 2. Add the new profile BZ.ONNT.BZAPP. If you are using a different application ID, change BZAPP to your application ID. ISPF client users must have AD access to this profile to generate PassTickets and login to the T repository. Follow the instructions in the sample member BZAFT in SBZSAMP, or if you are using the configuration utility, in the generated PassTicket command. Optionally, you can set the profile to BZ.ONNT.*, which enables all ISPF client application IDs to use the profile. PDS onsiderations: ational DOOS Next Generation uses the "partitioned data set extended" or PDS format for the SBZAUTH target library. There are some operational differences between PDS and PDS data sets. The PDS format may be shared by more than one z/os system and no special precautions are necessary. However the PDS format may only be shared by z/os systems which are part of a sysplex or which are connected using Global esource Serialization (are in a GS complex). If z/os systems share use of a PDS data set outside of a sysplex or GS environment, you may experience severe problems when the data set is updated. This is due to the fact that PDS directory information is cached in storage, and when the data set is updated from one system the other system(s) have no knowledge of the update, and their cached directory information will be incorrect. You must take care not to share the SBZAUTH data set between z/os systems unless they are in a sysplex or are connected in a GS complex. If you need to share the content of the SBZAUTH data set, a separate copy must be created for each z/os system. Installation equirements and onsiderations 23

30 6.0 Installation Instructions This chapter describes the installation method and the step-by-step procedures to install and to activate the functions of ational DOOS Next Generation. Please note the following points: If you want to install ational DOOS Next Generation into its own SMP/ environment, consult the SMP/ manuals for instructions on creating and initializing the SMPSI and the SMP/ control data sets. You can use the sample jobs that are provided to perform part or all of the installation tasks. The SMP/ jobs assume that all DDDF entries that are required for SMP/ execution have been defined in appropriate zones. You can use the SMP/ dialogs instead of the sample jobs to accomplish the SMP/ installation steps. 6.1 Installing ational DOOS Next Generation SMP/ onsiderations for Installing ational DOOS Next Generation Use the SMP/ IV, APPY, and APT commands to install this release of ational DOOS Next Generation SMP/ Options Subentry Values The recommended values for certain SMP/ SI subentries are shown in Figure 23. Using values lower than the recommended values can result in failures in the installation. DSSPA is a subentry in the GOBA options entry. PMAX is a subentry of the GNA entry in the GOBA options entry. See the SMP/ manuals for instructions on updating the global zone. Figure 23. SMP/ Options Subentry Values Subentry Value omment DSSPA (1500,1500,1500) 3390 DASD tracks PMAX SMP/ Default IBM recommends using the SMP/ default for PMAX. 24 opyright IBM orp. 2008, 2017

31 6.1.3 Overview of the installation steps Overview of steps required to install IBM ational DOOS Next Generation. 1. Upload sample J from the client 2. xpand the sample jcl file by using the TSO eceive command 3. Sample Jobs 4. un the job to allocate sequential data sets that the FTP step will use 5. Upload the compressed FIS and SMPMS from the client 6. xpand the FIs by running the sample job, BZXPND 7. Delete previous release of IBM ational DOOS Next Generation (optional) 8. reate SMP/ nvironment (optional) 9. Perform SMP/ IV 10. Allocate SMP/ target and distribution libraries 11. reate ZFS file system (optional) 12. Allocate file system paths 13. reate DDDF entries 14. Perform SMP/ APPY 15. Perform SMP/ APT Upload Sample J from the client On the client, there is a file containing sample installation J. This sample J contains a member (BZSQA) that will allocate the sequential data sets on z/os for the compressed FIs and SMPMS contained on the client and other members to perform the SMP/ processing. Perform the following steps to upload it from the client to z/os: 1. Allocate a data set on z/os to use as the target of the upload. You can do this by creating a data set with the characteristics from the job below or by submitting the job below. if you choose to submit the following job you need to make the following updates: a. Add a job card and modify the parameters to meet your site's requirements before submitting. b. hlq will be the high level qualifier you choose to use for this data set. c. (Optionally) eplace vvvvvv with the volser you choose to use for this data set. Installation Instructions 25

32 //AO X PGM=IFB14 // //JBIN DD DSN=hlq.IBM.H6 4.SMPJOBS.BIN, // DISP=(NW,ATG,DT), // DSOG=PS, // FM=FB, // =8, // BKSIZ=616, // VO=S=vvvvvv, // UNIT=SYSADA, // SPA=(TK,(15,1)) 2. Upload the sample jcl file in binary format from the client to this z/os data set. If the client is attached to a Windows system, you can use FTP from a command prompt to upload the file. In the sample dialog shown below, commands or other information entered by the user are in bold, and the following values are assumed: Figure 24. User ntered Values User enters: mvsaddr tsouid tsopw Values TP/IP address or hostname of the z/os system Your TSO user ID Your TSO password d: Your client drive hlq High-level qualifier you used for the data set you allocated in the job above :\>ftp mvsaddr onnected to mvsaddr. 22 -FTP Server (user ' _address') 22 User (mvsaddr:(none)): tsouid 331-Password: 331 Password: tsopw FTPD1 IBM FTP S V21 at mvsaddr, 1:18:2 on tsouid is logged on. Working directory is "tsouid.". 23 ftp> cd.. 25 ""is the working directory name prefix. ftp> cd hlq 25 "hlq." is the working directory name prefix. 26 ational DOOS Next Generation Program Directory

33 ftp> binary 2 epresentation type is Image ftp> put d:\h6 4\IBM.H6 4.F1.BIN 'hlq.ibm.h6 4.SMPJOBS.BIN' 125 Storing data set hlq.ibm.h6 4.SMPJOBS.BIN ftp: 2632 bytes sent in. 6 Seconds Kbytes/sec. ftp> quit 221 Quit command received. Goodbye xpand the sample jcl file by using the TSO eceive command: IV INDA('hlq.IBM.H6 4.SMPJOBS.BIN') When prompted on the TSO receive command, use the appropriate DSNAM as listed below: DS('hlq.IBM.H6 4.SMPJOBS') Sample Jobs The following sample installation jobs are provided as part of the product to help you install ational DOOS Next Generation. The FIs will be prefixed with the high level qualifier ("hlq" in table below) used when the files are "received". The jobs are contained in the sample J data set hlq.ibm.h604.smpjobs that was uploaded. Figure 25 (Page 1 of 2). Sample Installation Jobs Job Name Job Type Description FI BZSQA SMP/ Sample job to allocate sequential data sets for FTPing the product data sets into hlq.ibm.h604.f1 BZXPND SMP/ Sample job to expand the FIs hlq.ibm.h604.f1 BZD SMP/ Sample job to remove previous version(s) of IBM ational DOOS Next Generation from an existing SMP/ target and distribution libraries (optional) BZSMP SMP/ Sample job to create an SMP/ environment (optional) BZV1 IV Sample SMP/ IV job for ational ommon omponents BZV2 IV Sample SMP/ IV job for ational Jazz Team Server BZV3 IV Sample SMP/ IV job for hange and onfiguration Management hlq.ibm.h604.f1 hlq.ibm.h604.f1 hlq.ibm.h604.f1 hlq.ibm.h604.f1 hlq.ibm.h604.f1 Installation Instructions 27

34 Figure 25 (Page 2 of 2). Sample Installation Jobs Job Name Job Type Description FI BZV4 IV Sample SMP/ IV job for Quality Management BZV5 IV Sample SMP/ IV job for equirements Management BZV7 IV Sample SMP/ IV job for Build System Toolkit BZV8 IV Sample SMP/ IV job for ational Developer for z System subset BZV9 IV Sample SMP/ IV job for ational Build Agent BZVA IV Sample SMP/ IV job for ational Websphere iberty BZVB IV Sample SMP/ IV job for IBM Jazz eporting Services BZV IV Sample SMP/ IV job for ational Global onfiguration Management BZVD IV Sample SMP/ IV job for ational ngineering ifecycle Manager BZV IV Sample SMP/ IV job for ational ink Index Provider BZAO AOAT Sample job to allocate target and distribution libraries BZZFS AOMZF Sample job to create, format, and mount the data set for the ZFS file system (optional) BZISMKD MKDI Sample job to invoke the supplied BZMKDI X to allocate file system paths hlq.ibm.h604.f1 hlq.ibm.h604.f1 hlq.ibm.h604.f1 hlq.ibm.h604.f1 hlq.ibm.h604.f1 hlq.ibm.h604.f1 hlq.ibm.h604.f1 hlq.ibm.h604.f1 hlq.ibm.h604.f1 hlq.ibm.h604.f1 hlq.ibm.h604.f1 hlq.ibm.h604.f1 hlq.ibm.h604.f1 BZDDDF DDDF Sample job to define SMP/ DDDFs hlq.ibm.h604.f1 BZAPPY APPY Sample SMP/ APPY job hlq.ibm.h604.f1 BZAPT APT Sample SMP/ APT job hlq.ibm.h604.f1 28 ational DOOS Next Generation Program Directory

35 6.1.7 un the job to allocate sequential data sets that the FTP step will use dit and submit sample job BZSQA in the hlq.ibm.h604.smpjobs data set to allocate data sets on z/os to be used during the upload process. Use the instructions in the sample job for information on changes required. xpected eturn odes and Messages: = Upload the compressed FIS and SMPMS from the client Upload the files in binary format from the client to the z/os data set. If the client is a Windows system, you can use FTP from a command prompt to upload the files: :\>ftp mvsaddr onnected to mvsaddr. 22 -FTP Server (user ' _address') 22 User (mvsaddr:(none)): tsouid 331-Password: 331 Password: tsopw FTPD1 IBM FTP S V23 at mvsaddr, 5:36:25 on tsouid is logged on. Working directory is "tsouid.". 23 ftp> cd.. 25 ""is the working directory name prefix. ftp> cd hlq 25 "hlq." is the working directory name prefix. ftp> binary 2 epresentation type is Image ftp> prompt Interactive mode Off. If you are installing ational Jazz Team Server - HJS6 4: ftp> mput d:\hjs6 4\IBM.HJS6 4.F 125 Storing data set IBM.HJS6 4.F1.BIN ftp: bytes sent in. 3 Seconds Kbytes/sec. Installation Instructions 29

36 125 Storing data set IBM.HJS6 4.F2.BIN ftp: bytes sent in 3.73 Seconds Kbytes/sec. ftp> put d:\hjs6 4\IBM.HJS6 4.SMPMS 125 Storing data set IBM.HJS6 4.SMPMS ftp: 456 bytes sent in. 1 Seconds Kbytes/sec. If you are installing Build System Toolkit - HBT6 4: ftp> mput d:\hbt6 4\IBM.HBT6 4.F 125 Storing data set IBM.HBT6 4.F1.BIN ftp: bytes sent in. 7 Seconds Kbytes/sec. 125 Storing data set IBM.HBT6 4.F1.BIN ftp: 7616 bytes sent in.32 Seconds Kbytes/sec. 125 Storing data set IBM.HBT6 4.F2.BIN ftp: bytes sent in Seconds Kbytes/sec. 125 Storing data set IBM.HBT6 4.F3.BIN ftp: 5984 bytes sent in. 1 Seconds Kbytes/sec. 125 Storing data set IBM.HBT6 4.F4.BIN ftp: 98 8 bytes sent in. 3 Seconds Kbytes/sec. 125 Storing data set IBM.HBT6 4.F5.BIN ftp: 8832 bytes sent in.1 Seconds Kbytes/sec. 125 Storing data set IBM.HBT6 4.F6.BIN ftp: 98 8 bytes sent in. 3 Seconds Kbytes/sec. 125 Storing data set IBM.HBT6 4.F7.BIN ftp: 8832 bytes sent in.1 Seconds Kbytes/sec. 125 Storing data set IBM.HBT6 4.F8.BIN ftp: 1 24 bytes sent in. 3 Seconds Kbytes/sec. 30 ational DOOS Next Generation Program Directory