IBM Rational Developer for System z Version Configuration Guide SC

Transcription

1 IBM Rational Deeloper for System z Version Configuration Guide SC

2

3 IBM Rational Deeloper for System z Version Configuration Guide SC

4 Note Before using this document, read the general information under Documentation notices for IBM Rational Deeloper for System z on page 201. Ninth edition (Noember 2012) This edition applies to IBM Rational Deeloper for System z Version (program number 5724-T07) and to all subsequent releases and modifications until otherwise indicated in new editions. Order publications by phone or fax. IBM Software Manufacturing Solutions takes publication orders between 8:30 a.m. and 7:00 p.m. eastern standard time (EST). The phone number is (800) The fax number is (800) Faxes should be sent Attn: Publications, 3rd floor. You can also order publications through your IBM representatie or the IBM branch office sering your locality. Publications are not stocked at the address below. IBM welcomes your comments. You can send your comments by mail to the following address: IBM Corporation Attn: Information Deelopment Department 53NA Building 501 P.O. Box Research Triangle Park NC USA You can fax your comments to: (US and Canada) When you send information to IBM, you grant IBM a nonexclusie right to use or distribute the information in any way it beliees appropriate without incurring any obligation to you. Note to U.S. Goernment Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Copyright IBM Corporation 2000, US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures ii Tables ix About this document xi Who should use this document xi Summary of changes xii Description of document content xi Planning xi Basic customization xi (Optional) Common Access Repository Manager (CARMA) x (Optional) SCLM Deeloper Toolkit..... x (Optional) Application Deployment Manager.. x (Optional) Other customization tasks..... x Installation erification xi Security definitions xi Migration guide xi Operator commands xi Host configuration reference xi Chapter 1. Planning Migration considerations Planning considerations Product oeriew Skill requirements Time requirements Preinstallation considerations Installation user ID Requisite products Required resources Pre-configuration considerations Workload management Resource usage and system limits Required configuration of requisite products... 7 User ID considerations Serer considerations Configuration method Predeployment considerations Client checklist Chapter 2. Basic customization Requirements and checklist Customization setup PARMLIB changes Set z/os UNIX limits in BPXPRMxx Add started tasks to COMMNDxx LPA definitions in LPALSTxx APF authorizations in PROGxx LINKLIST definitions in PROGxx Requisite LINKLIST and LPA definitions LINKLIST definitions for other products PROCLIB changes JES Job Monitor RSE daemon Lock daemon JCL limitations for the PARM ariable ELAXF* remote build procedures Security definitions FEJJCNFG, JES Job Monitor configuration file rsed.enars, RSE configuration file Defining the PORTRANGE aailable for RSE serer Defining extra Jaa startup parameters with _RSE_JAVAOPTS Defining extra Jaa startup parameters with _RSE_ISPF_OPTS ISPF.conf, ISPF's TSO/ISPF Client Gateway configuration file Optional components Installation erification Chapter 3. (Optional) Common Access Repository Manager (CARMA) Requirements and checklist Select serer startup method and actie RAM CARMA serer startup Production RAMs Sample RAMs Preconfigured RAM and serer startup combinations CRASTART with CA Endeor SCM RAM Create CARMA VSAM data sets Customize CRASRV.properties Customize crastart.endeor.conf (Optional) Additional CA Endeor SCM RAM customization CRASTART with sample RAMs Create CARMA VSAM data sets Customize CRASRV.properties Customize crastart.conf Batch submit with CA Endeor SCM RAM Create CARMA VSAM data sets Customize CRASRV.properties Customize CRASUBCA (Optional) Additional CA Endeor SCM RAM customization Batch submit with sample RAMs Create VSAM data sets Customize CRASRV.properties Customize CRASUBMT CARMA configuration details CRASRV.properties, RSE interface to CARMA.. 59 crastart*.conf, CRASTART serer startup CRASUB*, batch submit serer startup CARMA VSAM data sets CARMA Repository Access Managers (RAMs).. 68 CRASHOW and CRATMAP, CA Endeor SCM RAM configuration files Copyright IBM Corp. 2000, 2012 iii

6 CRANDVRA, CA Endeor SCM RAM allocation exec CA Endeor SCM RAM batch actions CARMA return codes (Optional) Supporting multiple RAMs Example (Optional) Custom allocation exec (Optional) IRXJCL ersus CRAXJCL Create CRAXJCL Chapter 4. (Optional) SCLM Deeloper Toolkit Requirements and checklist Prerequisites ISPF.conf updates for SCLMDT rsed.enars updates for SCLMDT (Optional) Long/short name translation Create LSTRANS.FILE, the long/short name translation VSAM rsed.enars updates for long/short name translation (Optional) Install and customize Ant SCLM updates for SCLMDT Remoe old files from WORKAREA and /tmp.. 86 Chapter 5. (Optional) Application Deployment Manager Requirements and checklist CRD repository CICS administratie utility RESTful ersus Web Serice CRD serer using the RESTful interface CICS primary connection region CICS non-primary connection regions (Optional) Customize CRD serer transaction IDs 90 CRD serer using the Web Serice interface Pipeline message handler CICS primary connection region CICS non-primary connection regions (Optional) Manifest repository Chapter 6. (Optional) Other customization tasks (Optional) pushtoclient.properties, Host-based client control (Optional) ssl.properties, RSE SSL encryption (Optional) rsecomm.properties, RSE tracing (Optional) include.conf, Forced includes for C/C++ content assist (Optional) DB2 stored procedure Workload Manager (WLM) changes PROCLIB changes DB2 changes (Optional) z/os UNIX subprojects REXEC (or SSH) set up (Optional) Include preprocessor support (Optional) xunit support for Enterprise COBOL and PL/I (Optional) Enterprise Serice Tools support (Optional) CICS bidirectional language support 108 (Optional) Diagnostic IRZ messages for generated code (Optional) Problem Determination Tools support 110 (Optional) DB2 and IMS debug support (Optional) File Manager support (Optional) WORKAREA and /tmp cleanup Chapter 7. Installation erification Verify started tasks JMON, JES Job Monitor LOCKD, Lock daemon RSED, RSE daemon IVP operator commands PassTicket reusability RSE daemon connection ISPF Client Gateway Verify serices IVP initialization Port aailability TCP/IP setup RSE daemon connection JES Job Monitor connection Lock daemon connection ISPF's TSO/ISPF Client Gateway connection (Optional) CARMA connection (Optional) SCLMDT connection Chapter 8. Security definitions Requirements and checklist Actiate security settings and classes Define an OMVS segment for Deeloper for System z users Define the Deeloper for System z started tasks 132 Define RSE as a secure z/os UNIX serer Define MVS program controlled libraries for RSE 134 Define PassTicket support for RSE Define application protection for RSE Define JES command security Define data set profiles Define z/os UNIX program controlled files for RSE Verify security settings Chapter 9. Migration guide Migration considerations Backing up preiously configured files Version 8.5.x migration notes Migrate from ersion to ersion IBM Rational Deeloper for System z, FMID HHOP Configurable files Version 8.0.x migration notes Migrate from ersion 7.6 to ersion IBM Rational Deeloper for System z, FMID HHOP Configurable files Sample migration scenarios Migrate from ersion 7.5 to ersion IBM Rational Deeloper for System z, FMID HHOP i IBM Rational Deeloper for System z Version 8.5.1: Configuration Guide

7 Configurable files Migrate from ersion 7.1 to ersion IBM Rational Deeloper for System z, FMID HHOP Configurable files Chapter 10. Operator commands Start (S) JES Job Monitor RSE daemon Lock daemon Modify (F) JES Job Monitor RSE daemon Lock daemon Stop (P) Console messages JES Job Monitor RSE daemon, RSE thread pool serer, and lock daemon How to read a syntax diagram Symbols Operands Syntax example Nonalphanumeric characters and blank spaces 186 Selecting more than one operand Longer than one line Syntax fragments Understanding Deeloper for System z Security considerations TCP/IP considerations WLM considerations Tuning considerations Performance considerations Push-to-client considerations CICSTS considerations User exit considerations Customizing the TSO enironment Running multiple instances Troubleshooting configuration problems Setting up SSL and X.509 authentication Setting up TCP/IP Bibliography Referenced publications Informational publications Glossary Documentation notices for IBM Rational Deeloper for System z Copyright license Trademark acknowledgments Index Appendix. Host Configuration Reference Contents

8 i IBM Rational Deeloper for System z Version 8.5.1: Configuration Guide

9 Figures 1. JMON - JES Job Monitor started task RSED - RSE daemon started task LOCKD - Lock daemon started task RSED - alternate RSE daemon startup rsed.stdin.sh - alternate RSE daemon startup FEJJCNFG, JES Job Monitor configuration file rsed.enars - RSE configuration file rsed.enars - RSE configuration file (continued) rsed.enars - RSE configuration file (continued) ISPF.conf - ISPF configuration file CRASRV.properties - CRASTART with CA Endeor SCM RAM crastart.endeor.conf - CRASTART with CA Endeor SCM RAM CRASRV.properties - CRASTART with sample RAMs crastart.conf - CRASTART with sample RAMs CRASRV.properties - batch submit with CA Endeor SCM RAM CRASUBCA - batch submit with CA Endeor SCM RAM CRASRV.properties - batch submit with sample RAMs CRASUBMT - batch submit with sample RAMs CRASRV.properties CARMA configuration file crastart*.conf - CARMA serer startup using CRASTART CRASUB* - CARMA startup using batch submit CRASHOW - CA Endeor SCM RAM default filters CRATMAP - CA Endeor SCM RAM default filters CRABCFG - CA Endeor SCM RAM batch-action configuration CRABATCA - CA Endeor SCM RAM batch-action JCL CRABJOBC - CA Endeor SCM RAM batch-action JOB card ISPF.conf updates for SCLMDT rsed.enars updates for SCLMDT FLM02LST - long/short name translation setup JCL pushtoclient.properties - Host-based client control configuration file ssl.properties SSL configuration file rsecomm.properties Logging configuration file include.conf - Forced includes for C/C++ content assist ELAXMSAM - DB2 stored procedure task ELAXMJCL DB2 stored procedure definition START JMON operator command START RSED operator command START LOCKD operator command MODIFY JMON operator command MODIFY RSED operator command MODIFY LOCKD operator command STOP operator command Copyright IBM Corp. 2000, 2012 ii

10 iii IBM Rational Deeloper for System z Version 8.5.1: Configuration Guide

11 Tables 1. Required resources Optional resources Administrators needed for required tasks 4 4. Administrators needed for optional tasks 5 5. Client checklist - mandatory parts Client checklist - optional parts Match load modules to functions Sample ELAXF* procedures ELAXF* high-leel qualifier checklist LIMIT_COMMANDS command permission matrix CARMA return codes SCLM administrator checklist Default CRD serer transaction IDs Default CRD serer transaction IDs Push-to-client group support SSL certificate storage mechanisms Valid keystore types IVPs for serices Security setup ariables JES2 Job Monitor operator commands JES3 Job Monitor operator commands Version 8.5 customizations Version customizations Version 7.6 customizations Version 7.5 customizations Thread pool error status RSE console messages Referenced publications Referenced Web sites Informational publications Copyright IBM Corp. 2000, 2012 ix

12 x IBM Rational Deeloper for System z Version 8.5.1: Configuration Guide

13 About this document This document discusses the configuration of the IBM Rational Deeloper for System z functions. It includes instructions on how to configure IBM Rational Deeloper for System z Version on your z/os host system. From here on, the following names are used in this manual: IBM Rational Deeloper for System z is called Deeloper for System z. Common Access Repository Manager is abbreiated to CARMA. Software Configuration and Library Manager Deeloper Toolkit is called SCLM Deeloper Toolkit, abbreiated to SCLMDT. IBM z/os Automated Unit Testing Framework is called zunit. z/os UNIX System Serices is called z/os UNIX. Customer Information Control System Transaction Serer is called CICSTS, abbreiated to CICS. For earlier releases, including IBM WebSphere Deeloper for System z, IBM WebSphere Deeloper for zseries and IBM WebSphere Studio Enterprise Deeloper, use the configuration information found in the Host Configuration Guide and Program Directories for those releases. This document is part of a set of documents that describe Deeloper for System z host configuration. Each of these documents has a specific target audience. You are not required to read all documents to complete the Deeloper for System z configuration. Rational Deeloper for System z Host Configuration Guide (SC ) describes in detail all planning tasks, configuration tasks, and options (including optional ones) and proides alternatie scenarios. Rational Deeloper for System z Host Configuration Reference (SC ) describes Deeloper for System z design and gies background information for arious configuration tasks of Deeloper for System z, z/os components, and other products (such as WLM and CICS) related to Deeloper for System z. Rational Deeloper for System z Host Configuration Quick Start Guide (GI ) describes a minimal setup of Deeloper for System z. Rational Deeloper for System z Host Configuration Utility (SC ) describes the Host Configuration Utility, an ISPF panel application that guides you through basic and common optional customization steps for Deeloper for System z. The information in this document applies to all IBM Rational Deeloper for System z Version packages including IBM Rational Deeloper for zenterprise. Who should use this document This document is intended for system programmers installing and configuring IBM Rational Deeloper for System z Version This document lists in detail the different steps needed to do a full setup of the product, including some non-default scenarios. Background information that can help you plan and execute the configuration can be found in the IBM Rational Copyright IBM Corp. 2000, 2012 xi

14 Summary of changes Deeloper for System z Host Configuration Reference (SC ). To use this document, you need to be familiar with the z/os UNIX System Serices and MVS host systems. This section summarizes the changes for IBM Rational Deeloper for System z Version Host Configuration Guide, SC (updated Noember 2012). Technical changes or additions to the text and illustrations are indicated by a ertical line to the left of the change. This document contains information preiously presented inibm Rational Deeloper for System z Version 8.5 Host Configuration Guide, SC New information: Version migration information. See Version 8.5.x migration notes on page 147. New and changed directies in rsed.enars. See rsed.enars, RSE configuration file on page 30. Enhanced support for CA Endeor SCM RAM batch actions. See CA Endeor SCM RAM batch actions on page 71. Installation user ID requirements. See Installation user ID on page 2. This document contains information preiously presented in IBM Rational Deeloper for System z Host Configuration Guide, SC (updated June 2012). Technical changes or additions to the text and illustrations are indicated by a ertical line to the left of the change. This document contains information preiously presented in Rational Deeloper for System z Version Host Configuration Guide, SC New information: New optional directies in FEJJCNFG. See FEJJCNFG, JES Job Monitor configuration file on page 25. New optional directies in rsed.enars. See rsed.enars, RSE configuration file on page 30. New optional configuration file. See (Optional) include.conf, Forced includes for C/C++ content assist on page 101. New optional component. See (Optional) Include preprocessor support on page 106. New optional component. See (Optional) xunit support for Enterprise COBOL and PL/I on page 107. New optional component. See (Optional) DB2 and IMS debug support on page 110. New and enhanced operator commands. See Chapter 10, Operator commands, on page 173. Version 8.5 migration information. See Migrate from ersion to ersion 8.5 on page 148. Remoed information: xii IBM Rational Deeloper for System z Version 8.5.1: Configuration Guide

15 Support for File Manager Integration has changed, resulting in the remoal of most information in section (Optional) File Manager support on page 111. This document contains information preiously presented in Rational Deeloper for System z Version Host Configuration Guide, SC New information: New directies in rsed.enars. See rsed.enars, RSE configuration file on page 30. Added support for CA Endeor SCM background actions. See CA Endeor SCM RAM batch actions on page 71. Added support for CA Endeor SCM packages. See CARMA Repository Access Managers (RAMs) on page 68. New directies in pushtoclient.properties. See (Optional) pushtoclient.properties, Host-based client control on page 95. File Manager Integration is deprecated. See (Optional) File Manager support on page 111. New and enhanced operator commands. See Chapter 10, Operator commands, on page 173. Version migration information. See Version 8.0.x migration notes on page 154. Version sample migration scenarios. See Sample migration scenarios on page 162. New publication, IBM Rational Deeloper for System z Messages and Codes (SC ). This document contains information preiously presented in Rational Deeloper for System z Version Host Configuration Guide, SC New information: New directies in FEJJCNFG. See FEJJCNFG, JES Job Monitor configuration file on page 25. New directies in rsed.enars. See rsed.enars, RSE configuration file on page 30. The CARMA chapter has been reorganized, and some new information has been added. See Chapter 3, (Optional) Common Access Repository Manager (CARMA), on page 49. New configuration file pushtoclient.properties. See (Optional) pushtoclient.properties, Host-based client control on page 95. Version migration information. See Migrate from ersion 7.6 to ersion on page 156. Remoed information: The information preiously presented in Rational Deeloper for System z Version Host Configuration Guide (SC ) is now split into 2 documents: Rational Deeloper for System z Host Configuration Guide (SC ) and Rational Deeloper for System z Host Configuration Reference (SC ). Information regarding APPC setup has moed to white paper Using APPC to proide TSO command serices (SC ). Information regarding CARMA using ISPF Client Gateway has moed to white paper Using ISPF Client Gateway to proide CARMA serices (SC ). About this document xiii

16 (Optional) Host based property groups section in (Optional) Other customization tasks (described propertiescfg.properties). (Optional) Host based projects section in (Optional) Other customization tasks (described projectcfg.properties). (Optional) Uneditable characters section in (Optional) Other customization tasks (described uchars.settings). Version migration notes section in Migration guide. This document contains information preiously presented in Rational Deeloper for System z Version 7.6. Host Configuration Guide, SC New information: Corrections and additional information presented in Rational Deeloper for System z 7.6 Host Configuration Release Notes are incorporated. Version specific migration notes. Added document oeriew. See Description of document content. Support for 64-bit Jaa. See Rational Deeloper for System z Prerequisites (SC ). Product configuration through ISPF panels. See Pre-configuration considerations on page 6. New directies in rsed.enars. See rsed.enars, RSE configuration file on page 30. New proclib members. See ELAXF* remote build procedures on page 23. New CARMA VSAM layout. See CARMA VSAM migration notes on page 67. Supporting multiple CARMA RAMs. See (Optional) Supporting multiple RAMs on page 75. New Application Deployment Manager options. See "Administratie utility" in the Host Configuration Reference (SC ). New Application Deployment Manager VSAM layout. See "Administratie utility migration notes" in the Host Configuration Reference (SC ). New operator commands. See Chapter 10, Operator commands, on page 173. New console messages. See Console messages on page 183. Workload Management information. See "WLM considerations" in the Host Configuration Reference (SC ). Description of document content This section summarizes the information presented in this document. Planning Use the information in this chapter to plan the installation and deployment of Deeloper for System z. Basic customization The following customization steps are for a basic Deeloper for System z setup: Customization setup on page 13 PARMLIB changes on page 14 PROCLIB changes on page 20 Security definitions on page 25 xi IBM Rational Deeloper for System z Version 8.5.1: Configuration Guide

17 FEJJCNFG, JES Job Monitor configuration file on page 25 rsed.enars, RSE configuration file on page 30 ISPF.conf, ISPF's TSO/ISPF Client Gateway configuration file on page 46 (Optional) Common Access Repository Manager (CARMA) Common Access Repository Manager (CARMA) is a serer platform for Repository Access Managers (RAMs). A RAM is an Application Programming Interface (API) for a z/os based Software Configuration Manager (SCM). By wrapping the SCM functionality in a RAM, a single API is aailable for a client to access any supported SCM. Deeloper for System z proides multiple pre-built RAMs, as well as source code examples for creating your own RAM. The IBM Rational Deeloper for System z Interface for CA Endeor Software Configuration Manager gies Deeloper for System z clients direct access to CA Endeor SCM. (Optional) SCLM Deeloper Toolkit SCLM Deeloper Toolkit proides the tools needed to extend the capabilities of SCLM to the client. SCLM itself is a host-based source code manager that is shipped as part of ISPF. The SCLM Deeloper Toolkit has an Eclipse-based plug-in that interfaces to SCLM and proides for access to all SCLM processes for legacy code deelopment as well as support for full Jaa and J2EE deelopment on the workstation with synchronization to SCLM on the mainframe including building, assembling, and deployment of the J2EE code from the mainframe. (Optional) Application Deployment Manager Deeloper for System z uses certain functions of Application Deployment Manager as a common deployment approach for arious components. Optional customization enables more features of Application Deployment Manager and can add the following serices to Deeloper for System z: IBM CICS Explorer proides an Eclipse-based infrastructure to iew and manage CICS resources and enables greater integration between CICS tools. CICS Resource Definition (CRD) client and serer proide the following functions: CICS Resource Definition editor Allow application deelopers to define CICS resources in a limited, controlled, and secure fashion. Preent CICS deelopment access to unauthorized or incorrect VSAM data sets by proiding the CICS administrator control oer the physical data set name attribute in File definitions. Miscellaneous CICS deelopment aids Miscellaneous CICS Web Serice deelopment aids (Optional) Other customization tasks This section combines a ariety of optional customization tasks. Follow the instructions in the appropriate section to configure the desired serice. Customizations to Deeloper for System z configuration files: About this document x

18 pushtoclient.properties, Host-based client control ssl.properties, RSE SSL encryption rsecomm.properties, RSE tracing include.conf, Forced includes for C/C++ content assist Deeloper for System z related customizations to (or for) other products: DB2 stored procedure z/os UNIX subprojects Include preprocessor support xunit support for Enterprise COBOL and PL/I Enterprise Serice Tools support CICS bidirectional language support Diagnostic IRZ messages for generated code Problem Determination Tools support DB2 and IMS debug support File Manager support WORKAREA and /tmp cleanup Installation erification After completing the product customization, you can use the Installation Verification Programs (IVPs) described in this chapter to erify the successful setup of key product components. Security definitions This section describes the required and optional security definitions with sample RACF commands. Migration guide This section highlights installation and configuration changes compared to preious releases of the product. It also gies some general guidelines to migrate to this release. Operator commands This section proides an oeriew of the aailable operator (or console) commands for Deeloper for System z. Host configuration reference This section summarizes the information in IBM Rational Deeloper for System z Host Configuration Reference (SC ). xi IBM Rational Deeloper for System z Version 8.5.1: Configuration Guide

19 Chapter 1. Planning Migration considerations Planning considerations Use the information in this chapter, IBM Rational Deeloper for System z Prerequisites (SC ), to plan the installation and deployment of Deeloper for System z. The following subjects are described: Migration considerations Planning considerations Preinstallation considerations on page 2 Pre-configuration considerations on page 6 Predeployment considerations on page 9 Client checklist on page 10 Chapter 9, Migration guide, on page 145 describes installation and configuration changes compared to preious releases of the product. Use this information to plan your migration to the current release of Deeloper for System z. Note: If you are a preious user of IBM Rational Deeloper for System z, IBM WebSphere Deeloper for System z, IBM WebSphere Deeloper for zseries or IBM WebSphere Studio Enterprise Deeloper, it is recommended that you sae the related customized files BEFORE installing IBM Rational Deeloper for System z Version Refer to Chapter 9, Migration guide, on page 145 for an oeriew of files that required customization. Refer to "Running multiple instances" in the Host Configuration Reference (SC ), if you plan on running multiple instances of Deeloper for System z. Product oeriew Deeloper for System z consists of a client, installed on the user's personal computer, and a serer, installed on one or more hosts. This documentation will focus on the host being a z/os system. Howeer, other operating systems, such as AIX and Linux on System z, are also supported. The client proides deelopers an Eclipse-based deelopment enironment that facilitates a uniform graphical interface to the host, and that, among other things, can offload work from the host to the client, saing resources on the host. The host portion consists of seeral permanently actie tasks and tasks that are started ad-hoc. These tasks allow the client to work with the arious components of your z/os host, such as MVS data sets, TSO commands, z/os UNIX files and commands, job submit, and job output. Deeloper for System z can also interact with subsystems and other application software on the host, such as CICS, Debug Tool, and Software Configuration Managers (SCMs), if Deeloper for system z is configured to do so, and if these (corequisite) products are aailable. Copyright IBM Corp. 2000,

20 Refer to "Understanding Deeloper for System z" in the Host Configuration Reference (SC ) to get a basic understanding of the Deeloper for System z design. Refer to the Deeloper for System z web site, rational/products/deeloper/systemz/, or your local IBM representatie to learn more about the functionality offered by Deeloper for System z. Skill requirements Minimal SMP/E skills are needed for a Deeloper for System z host installation. The configuration of Deeloper for System z requires more than the typical system programming permissions and expertise, so assistance from others might be needed. Table 3 on page 4 and Table 4 on page 5 list the administrators needed for the required and optional customization tasks. Time requirements The amount of time required to install and configure the Deeloper for System z host components depends on arious factors, such as: the current z/os UNIX and TCP/IP configuration the aailability of prerequisite software and maintenance whether or not OMVS segments are defined for Deeloper for System z users the aailability 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 of the Deeloper for System z host requires from one to four days to complete. This time requirement is for a clean installation performed by an experienced system programmer. If problems are encountered, or if the required skills are not aailable, then the setup will take longer. Preinstallation considerations Refer to Program Directory for IBM Rational Deeloper for System z (GI ) for detailed instructions on the SMP/E installation of the product. Refer to "Running multiple instances" in the Host Configuration Reference (SC ) if you plan on running multiple instances of Deeloper for System z. The file system (HFS or zfs) in which Deeloper for System z is installed must be mounted with the SETUID permission bit on (this is the system default). Mounting the file system with the NOSETUID parameter will preent Deeloper for System z from creating the user's security enironment, and will fail the connection request of the client. The same is true for the file systems hosting Jaa and z/os UNIX binaries. Installation user ID The user ID used to install Deeloper for System z, or to install maintenance, must hae (at least) the following attributes: TSO access (with a normal region size). An OMVS segment defined to the security system (for example, RACF), both for the 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). 2 IBM Rational Deeloper for System z Version 8.5.1: Configuration Guide

21 The PROGRAM field in the OMVS segment should be /bin/sh or other alid z/os UNIX shell, such as /bin/tcsh. The user ID s default group requires a GID. UID=0 or READ authorization to the BPX.SUPERUSER profile in the FACILITY class. If the BPX.FILEATTR.APF or BPX.FILEATTR.PROGCTL profiles are defined in the FACILITY class, then the user ID must hae READ access to these profiles. READ, WRITE, and EXECUTE access to the /tmp directory (or a directory referenced in the TMPDIR enironment ariable). Requisite products IBM Rational Deeloper for System z Prerequisites (SC ) has a list of prerequisite software that must be installed and operational before Deeloper for System z will work. There is also a list of corequisite software to support specific features of Deeloper for System z. These requisites must be installed and operational at runtime for the corresponding feature to work as designed. Plan ahead to hae these requisite products aailable, as it might take some time, depending on the policies at your site. The key requisites for a basic setup are the following: z/os 1.8 or higher ISPF APAR OA38740 (TSO/ISPF Client Gateway) Jaa 6.0 or higher (31 or 64 bit) Required resources Deeloper for System z requires the allocation of the systems resources listed in Table 1. The resources listed in Table 2 on page 4 are required for optional serices. Plan ahead to hae these resources aailable, as it might take some time to get them, depending on the policies at your site. Table 1. Required resources Resource Default alue Information APF authorized data set FEK.SFEKAUTH APF authorizations in PROGxx on page 16 started task JMON, RSED, and LOCKD PROCLIB changes on page 20 port for host-confined use (JMON) port for host-confined use (LOCKD) port for client-host communication (RSED) port range for client-host communication (RSED) z/os UNIX serer security definition 6715 FEJJCNFG, JES Job Monitor configuration file on page rsed.enars, RSE configuration file on page rsed.enars, RSE configuration file on page 30 any aailable port is used UPDATE permission to BPX.SERVER for RSED started task Defining the PORTRANGE aailable for RSE serer on page 39 Define RSE as a secure z/os UNIX serer on page 133 Chapter 1. Planning 3

22 Table 1. Required resources (continued) Resource Default alue Information PassTicket security definitions no default Define PassTicket support for RSE on page 135 MVS build procedures ELAXF* PROCLIB changes on page 20 Table 2. Optional resources Resource Default alue Information LINKLIST data set FEK.SFEKAUTH and FEK.SFEKLOAD Chapter 4, (Optional) SCLM Deeloper Toolkit, on page 79 LPA data set FEK.SFEKLPA Chapter 3, (Optional) Common Access Repository Manager (CARMA), on page 49 port range for host-confined use port for client-host communication (100 ports) Chapter 3, (Optional) Common Access Repository Manager (CARMA), on page for Web Serice or 5130 for RESTful Chapter 5, (Optional) Application Deployment Manager, on page 87 CICS CSD update multiple alues Chapter 5, (Optional) Application Deployment Manager, on page 87 CICS JCL update FEK.SFEKLOAD Chapter 5, (Optional) Application Deployment Manager, on page 87 security definitions LDAP definitions FEK.PTC.* profiles for push-to-client FEK.PTC.* groups for push-to-client (Optional) CICS bidirectional language support on page 108 Push-to-client considerations in the Host Configuration Reference (SC ) Push-to-client considerations in the Host Configuration Reference (SC ) The configuration of Deeloper for System z requires more than the typical system programming permissions and expertise, so minimal assistance from others might be needed. Table 3 and Table 4 on page 5 list the administrators needed for the required and optional customization tasks. Table 3. Administrators needed for required tasks Administrator Task Information System Typical system programmer actions are required for all customization tasks N/A 4 IBM Rational Deeloper for System z Version 8.5.1: Configuration Guide

23 Table 3. Administrators needed for required tasks (continued) Administrator Task Information Security Define OMVS segment for Deeloper for System z users Define data set profiles Define started tasks Define operator command security Define z/os UNIX serer profiles Define application security Define PassTicket support Define program controlled data sets Define program controlled z/os UNIX files "Security considerations" in Host Configuration Reference (SC ) TCP/IP Define new TCP/IP ports "TCP/IP considerations" in Host Configuration Reference (SC ) WLM Assign started task goals to the serers and their child processes "WLM considerations" in the Host Configuration Reference (SC ). Table 4. Administrators needed for optional tasks Administrator Task Information System Typical system programmer actions are required for all customization tasks N/A Security Define data set profiles Define program controlled data sets Define permission to submit xxx* jobs Define CICS transaction security Add certificate for SSL Define X.509 client certificate support Define groups and profiles for push-to-client "Security considerations" in Host Configuration Reference (SC ) "CICSTS considerations" in the Host Configuration Reference (SC ) "Setting up SSL and X.509 authentication" in the Host Configuration Reference (SC ) "Push-to-client considerations in the Host Configuration Reference (SC ) TCP/IP Define new TCP/IP ports "TCP/IP ports" in Host Configuration Reference (SC ) SCLM Define SCLM language translators for JAVA/J2EE support Define SCLM types for JAVA/J2EE support Chapter 4, (Optional) SCLM Deeloper Toolkit, on page 79 Chapter 1. Planning 5

24 Table 4. Administrators needed for optional tasks (continued) Administrator Task Information CICS TS Update CICS region JCL Update CICS region CSD Define CICS group Define CICS transaction names Define a program to CICS DB2 Define a DB2 stored procedure WLM Assign goals to a DB2 stored procedure Assign goals to Deeloper for System z tasks LDAP Define groups for push-to-client Chapter 5, (Optional) Application Deployment Manager, on page 87 (Optional) CICS bidirectional language support on page 108 (Optional) DB2 stored procedure on page 103 (Optional) DB2 stored procedure on page 103 "WLM considerations" in the Host Configuration Reference (SC ) Push-to-client considerations in the Host Configuration Reference (SC ) Pre-configuration considerations Refer to Host Configuration Reference (SC ) for information about Deeloper for System z itself and how it interacts with your system and with the prerequisite and corequisite products. This information can assist you in creating a setup that supports your current needs and future growth. Workload management Unlike traditional z/os applications, Deeloper for System z is not a monolithic application that can be identified easily to Workload Manager (WLM). Deeloper for System z consists of seeral components that interact to gie the client access to the host serices and data. Refer to "WLM considerations" in the Host Configuration Reference (SC ) to plan your WLM configuration accordingly. Note: Deeloper for System z consists of multiple tasks that communicate with each other and the client. These tasks use arious timers to detect communication loss with their partner or partners. This implies that timeout issues can arise (due to lack of CPU time during the timeout window) on systems with a heay CPU load or incorrect Workload Management (WLM) settings for Deeloper for system z. Resource usage and system limits When in use, Deeloper for System z will use a ariable number of system resources like address spaces and z/os UNIX processes and threads. The aailability of these resources is limited by arious system definitions. Refer to "Tuning considerations" in the Host Configuration Reference (SC ) to estimate the usage of key resources, so you can plan your system configuration accordingly. Note that Deeloper for System z can run in either 31-bit or 64-bit mode, changing the storage resource limitations drastically. 6 IBM Rational Deeloper for System z Version 8.5.1: Configuration Guide

25 Required configuration of requisite products Consult your MVS system programmer, security administrator and TCP/IP administrator to check if the requisite products and software are installed, tested, and working. Some requisite customization tasks that are easily oerlooked are listed here: All Deeloper for System z users must hae READ and EXECUTE access to the Jaa directories. Remote (host-based) actions for z/os UNIX subprojects require that z/os UNIX ersion of REXEC or SSH is actie on the host. User ID considerations The user ID of a Deeloper for System z user must hae (at least) the following attributes: TSO access (with a normal region size). Note: A large region size is required for the user ID that executes the Installation Verification Programs (IVPs), because functions requiring a lot of memory (such as Jaa) will be executed. You should set the region size to kilobytes (128 megabytes) or higher. An OMVS segment defined to the security system (for example, RACF), both for the 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 alid z/os UNIX shell, such as /bin/tcsh. The ASSIZEMAX field should not be set, so that system defaults will be used. The user ID does not require UID 0. Example (command LISTUSER userid NORACF OMVS): USER=userid OMVS INFORMATION UID= HOME= /u/userid PROGRAM= /bin/sh CPUTIMEMAX= NONE ASSIZEMAX= NONE FILEPROCMAX= NONE PROCUSERMAX= NONE THREADSMAX= NONE MMAPAREAMAX= NONE The user ID s default group requires a GID. Example (command LISTGRP group NORACF OMVS): GROUP group OMVS INFORMATION GID= READ and EXECUTE access to the Deeloper for System z installation and configuration directories and files, default /usr/lpp/rdz/*, /etc/rdz/*, and /ar/rdz/*. READ, WRITE, and EXECUTE access to the Deeloper for System z WORKAREA directory, default /ar/rdz/workarea, and user log directory, default /ar/rdz/logs. Chapter 1. Planning 7

26 READ access to the Deeloper for System z installation data sets, default FEK.SFEK*. READ, WRITE, and EXECUTE access to the /tmp directory (or a directory referenced in the TMPDIR enironment ariable). Serer considerations Deeloper for System z consists of three permanently actie serers, which can be started tasks or user jobs. These serers proide the requested serices themseles, or start other serers (as z/os UNIX threads or user jobs) to proide the serice. JES Job Monitor (JMON) proides all JES-related serices. Lock Daemon (LOCKD) proides tracking serices for data set locks. Remote Systems Explorer (RSE) proides core serices such as connecting the client to the host and starting other serers for specific serices. RSE consists of two logical entities: RSE daemon (RSED), which manages connection setup and which is responsible for running in single serer mode. RSE serer, which handles indiidual client request. JES Job Monitor (JMON) proides all JES related serices. The security mechanisms used by JES Job Monitor rely on the data sets it resides in being secure. This implies that only trusted system administrators should be able to update the libraries and configuration files. Remote Systems Explorer (RSE) is the Deeloper for System z component that proides core serices such as connecting the client to the host. Since ersion 7.5, RSE daemon is no longer an INETD managed process but a started task. Since ersion 7.5, RSE serer uses a single serer model whereas with preious ersions, each client-host connection had a priate RSE serer. Different leels of communication security are supported by RSE: External (client-host) communication can be limited to specified ports. This feature is disabled by default. External (client-host) communication can be encrypted using SSL. This feature is disabled by default. Port Of Entry (POE) checking can be used to allow access only to trusted TCP/IP addresses. This feature is disabled by default. RSE also supports multiple client authentication methods: User ID and password User ID and one-time password X.509 certificate The security mechanisms used by RSE rely on the file system it resides in being secure. This implies that only trusted system administrators should be able to update the libraries and configuration files. The user IDs assigned to the RSED and LOCKD started tasks must hae READ, WRITE, and EXECUTE access to their home directory if /tmp is not aailable for WRITE access. As documented in "TCP/IP ports" in Host Configuration Reference (SC ), certain host serices, and thus their ports, must be aailable for the client to connect to, and must be defined to your firewall protecting the host. All other 8 IBM Rational Deeloper for System z Version 8.5.1: Configuration Guide

27 ports used by Deeloper for System z hae host-only traffic. Listed below are the ports needed for external communication in a basic Deeloper for System z setup. RSE daemon for client-host communication setup (using the tcp protocol), default port RSE serer for client-host communication (using the tcp protocol). By default, any aailable port is used, but this can be limited to a specified range. Configuration method Deeloper for System z proides alternatie methods to configure the host side of the product. This gies you a choice of the following methods: Predeployment considerations Using the Host Configuration Utility. This ISPF panel application guides you through the required customization steps and selected optional customization steps. For more information, refer to the Host Configuration Utility (SC ). Using the Host Configuration Quick Start Guide. This guides you through the required customization steps. The scope of this guide is limited to a basic setup. Using the Host Configuration Guide. This guides you through the required customization steps and all optional customization steps. All configurable options are coered in this guide, including some non-default scenarios Deeloper for System z supports cloning an installation to a different system, aoiding the need for a SMP/E installation on each system. The following data sets, directories, and files are mandatory for deployment to other systems. If you copied a file to a different location, then this file must replace its counterpart in the following lists. Note: The following list does not coer the deployment needs of the pre- and corequisite software. FEK.SFEKAUTH(*) FEK.SFEKLMOD(*) FEK.SFEKLOAD(*) FEK.SFEKPROC(*) FEK.#CUST.PARMLIB(*) FEK.#CUST.PROCLIB(*) /usr/lpp/rdz/* /etc/rdz/* /ar/rdz/* (directory structure only) optional parts: FEK.SFEKLPA(*) FEK.#CUST.CNTL(*) definitions, data sets, files, and directories resulting from customization jobs in FEK.#CUST.JCL Note: FEK and /usr/lpp/rdz are the high-leel qualifier and path used during the installation of the product. FEK.#CUST, /etc/rdz and /ar/rdz are the default locations used during the customization of the product (see Customization setup on page 13 for more information). Chapter 1. Planning 9

28 Client checklist You should install Deeloper for System z in a priate file system (HFS or zfs) to easy deploying the z/os UNIX parts of the product. If you cannot use a priate file system, you should use an archiing tool such as the z/os UNIX tar command to transport the z/os UNIX directories from system to system. This to presere the attributes (such as program control) for the Deeloper for System z files and directories. Refer to UNIX System Serices Command Reference (SA ) for more information about the following sample commands to archie and restore the Deeloper for System z installation directory. Archie: cd /SYS1/usr/lpp/rdz; tar -csf /u/userid/rdz.tar Restore: cd /SYS2/usr/lpp/rdz; tar -xsf /u/userid/rdz.tar Users of the Deeloper for System z client must know the result of certain host customizations, such as TCP/IP port numbers, for the client to work properly. Use these 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 RSE daemon TCP/IP port number (default 4035): Value See RSE daemon on page 21. Table 6. Client checklist - optional parts Customization Location of the ELAXF* procedures if they are not in a system procedure library (default FEK.#CUST.PROCLIB): See note on JCLLIB in ELAXF* remote build procedures on page 23. Procedure or step names of the ELAXF* procedures if they were changed: See note on changing them in ELAXF* remote build procedures on page 23. DB2 stored procedure name (default ELAXMSAM): See information about DB2 stored procedures in "Running multiple instances" in the Host Configuration Reference (SC ). Location of the DB2 stored procedure if it is not in a system procedure library: See (Optional) DB2 stored procedure on page 103. Location of the FEKRNPLI Include Preprocessor exec (default FEK.#CUST.CNTL): See (Optional) Include preprocessor support on page 106. Location of the unit test load modules if not in LINKLIST or STEPLIB of rsed.enars (default FEK.SFEKLOAD): See (Optional) xunit support for Enterprise COBOL and PL/I on page 107. Value 10 IBM Rational Deeloper for System z Version 8.5.1: Configuration Guide