Note: Before using this information, be sure to read the general information under Notices.
|
This edition applies to IBM® Rational® Developer for z Systems™ Version 9.5.1 (program number 5724-T07, or part of program number 5697-CDT) 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) 879-2755. The fax number is (800) 445-9269. Faxes should be sent Attn: Publications, 3rd floor.
You can also order publications through your IBM representative or the IBM branch office serving 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 Development Department 53NA
Building 501 P.O. Box 12195
Research Triangle Park NC 27709-2195
USA
You can fax your comments to: 1-800-227-5088 (US and Canada)
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
© Copyright IBM Corporation 2000, 2015
Note to U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This document discusses the configuration of the IBM Rational Developer for z Systems functions. It includes instructions to configure IBM Rational Developer for z Systems Version 9.5.1 on your z/OS® host system.
The information in this document applies to all IBM Rational Developer for z Systems Version 9.5 packages.
For the most up-to-date versions of this document, see the IBM Rational Developer for z Systems Host Configuration Guide (SC23-7658) available at http://www-05.ibm.com/e-business/linkweb/publications/servlet/pbi.wss?CTY=US&FNC=SRX&PBL=SC27-8577.
For the most up-to-date versions of the complete documentation, including installation instructions, white papers, podcasts, and tutorials, see the library page of the IBM Rational Developer for z Systems website (http://www-01.ibm.com/software/sw-library/en_US/products/Z964267S85716U24/).
This document is intended for system programmers who are installing and configuring IBM Rational Developer for z Systems Version 9.5.1.
This document lists in detail the steps that are needed to do a full setup of the product, including some non-default scenarios. Background information that can help you to plan and execute the configuration can be found in the IBM Rational Developer for z Systems Host Configuration Reference (SC27-8578). To use this document, you must be familiar with the z/OS UNIX System Services and MVS™ host systems.
This section summarizes the changes for IBM Rational Developer for z Systems Version 9.5.1 Host Configuration Guide, SC27-8577-00 (updated December 2015).
Technical changes or additions to the text and illustrations are indicated by a vertical line to the left of the change.
New information:
Removed information:
In version 9.5.1, the RSE and JES Job Monitor related functions moved from IBM Rational Developer for z Systems to another product, IBM Explorer for z/OS. This move includes the related documentation.
This document contains information that was previously
given in IBM
Rational Developer for z Systems Version
9.5 Host Configuration Guide, SC23-7658-14.
New information:
Moved information:
Removed information:
This document contains information that was previously given in IBM Rational Developer for z Systems Version 9.1.1 Host Configuration Guide, SC23-7658-13.
New information:
This document contains information that was previously given in IBM Rational Developer for z Systems Version 9.1 Host Configuration Guide, SC23-7658-12.
New information:
This document contains information that was previously given in IBM Rational Developer for z Systems Version 9.0.1 Host Configuration Guide, SC23-7658-11.
New information:
This document contains information that was previously given in IBM Rational Developer for z Systems Version 9.0.1 Host Configuration Guide, SC23-7658-10.
New information:
This document contains information that was previously given in IBM Rational Developer for z Systems Version 9.0 Host Configuration Guide, SC23-7658-09.
This document contains information that was previously given in IBM Rational Developer for z Systems Version 8.5.1 Host Configuration Guide, SC23-7658-08.
This document contains information that was previously given in IBM Rational Developer for z Systems Version 8.5 Host Configuration Guide, SC23-7658-07.
This section summarizes the information that is given in this document.
Use the information in this chapter to plan the installation and deployment of Developer for z Systems.
Common Access Repository Manager (CARMA) is a server platform for Repository Access Managers (RAMs). A RAM is an Application Programming Interface (API) for a Software Configuration Manager (SCM) that is based on a z/OS system. By wrapping the SCM functionality in a RAM, a single API is available for a client to access any supported SCM.
Developer for z Systems provides multiple pre-built RAMs and source code examples for creating your own RAM.
The IBM Rational Developer for z Systems Interface for CA Endevor® Software Configuration Manager gives Developer for z Systems clients direct access to CA Endevor® SCM.
SCLM Developer Toolkit provides the tools that are needed to extend the capabilities of SCLM to the client. SCLM itself is a host-based source code manager that is included in ISPF.
The SCLM Developer Toolkit has an Eclipse-based plug-in that interfaces to SCLM and provides access to all SCLM processes for heritage code development and support for full Java™ and J2EE development on the workstation with synchronization to SCLM on the mainframe. The synchronization activities include building, assembling, and deployment of the J2EE code from the mainframe.
The Developer for z
Systems Integrated
Debugger host component allows clients to debug various Language Environment® (LE) based
applications..
Similar to the Developer for z Systems client, the Developer for z Systems host supports running code analysis tools, which are provided as a separate product, IBM Rational Developer for z Systems Host Utilities. A benefit of doing code analysis on the host is that it can be integrated in your daily batch processing.
This section combines a variety of optional customization tasks. To configure the required service, follow the instructions in the appropriate section.
After completing the product customization, you can verify the successful setup of key product components by using the Installation Verification Programs (IVPs) described in this chapter.
This section describes the required and optional security definitions with sample RACF® commands.
This section highlights the installation and configuration changes compared to the previous releases of the product. It also gives some general guidelines to migrate to this release.
This section summarizes the information in Rational
Developer for z Systems Host
Configuration Reference (SC27-8578).
For a complete listing of the Developer for z Systems hardware and software requirements including prerequisites and co-requisites, see the System Requirements tab on the Developer for z Systems product page .
Migration guide describes the installation and configuration changes compared to previous releases of the product. Use this information to plan your migration to the current release of Developer for z Systems.
In version 9.5.1, Developer for z Systems became a product that installs on top of IBM Explorer for z/OS. Ensure you have a supported version of IBM Developer for z/OS.
Developer for z
Systems consists
of a client, installed on the user's personal computer, and a server,
installed on one or more host systems. Both client and host are installed
on top of IBM Explorer for z/OS. This documentation contains
information for a z/OS host
system.
The client provides developers with an Eclipse-based development environment that facilitates a uniform graphical interface to the host, and that, among other things, can offload work from the host to the client, saving resources on the host.
The host portion consists of several permanently active tasks and tasks that are started ad hoc. These tasks allow the client to work with the various components of your z/OS host system, such as MVS data sets, TSO commands, z/OS UNIX files and commands, job submit, and job output.
Developer for z
Systems enhances the basic access functionality provided
by z/OS Explorer. Developer for z
Systems can, for example, interact with subsystems and
other application software on the host system, such as CICS, and Software Configuration Managers (SCMs),
if Developer for z
Systems is
configured to do so, and if these co-requisite products are available.
For information about Developer for z
Systems itself,
how it interacts with your system, and with the prerequisite and co-requisite
products, see the Rational
Developer for z Systems Host
Configuration Reference (SC27-8578). The IBM Explorer for z/OS Host
Configuration Reference (SC27-8438) gives similar information
for z/OS Explorer, which is
a requisite for Developer for z
Systems.
To learn more about the functionality that is offered by Developer for z Systems, see the Developer for z Systems website, http://www-03.ibm.com/software/products/en/developerforsystemz/, or your local IBM representative.
SMP/E skills are needed for a Developer for z Systems host installation.
The configuration of Developer for z Systems requires more than the typical system programming permissions and expertise, so assistance from others might be needed. Table 3 and Table 4 list the administrators who are needed for the required and optional customization tasks.
Experience has shown that the installation and configuration
process of the Developer for z
Systems host
system requires from one to two days to complete and does not include
the installation and configuration of IBM Explorer
for z/OS, which is a required
product. . 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 available, the setup will take longer.
For detailed instructions on the SMP/E installation of the product, see Program Directory for IBM Rational Developer for z Systems (GI11-8298).
The Developer for z Systems servers are single-system minded, and are not SYSPLEX aware. If you are using the servers in a SYSPLEX, you must ensure that the data requested by the end users (data sets, job output, z/OS UNIX files) is available on the system Developer for z Systems is installed. See Predeployment considerations for cloning Developer for z Systems to other systems.
To run multiple instances of Developer for z Systems on a single host system, see "Running multiple instances" in the Rational Developer for z Systems Host Configuration Reference (SC27-8578) .
The file system (HFS or zFS) in which Developer for z Systems is installed must be mounted with the SETUID permission bit on (this is the system default). Mounting the file system with the NOSETUID parameter prevents Developer for z Systems from creating the user's security environment, and rejects the connection requests of the client. The same is true for the file systems hosting z/OS Explorer, Java, and z/OS UNIX binaries.
Developer for z Systems has a list of prerequisite software that must be installed and operational before the product will work. There is also a list of corequisite software to support specific features of Developer for z Systems. These requisites must be installed and operational at runtime for the corresponding features to work as designed.
For a complete listing of the Developer for z Systems software requirements including prerequisites and co-requisites, see the System Requirements tab on the Developer for z Systems website .
Developer for z Systems requires the allocation of the systems resources listed in Table 1. The resources listed in Table 2 are required for optional services. Plan to have these resources available because, depending on the policies at your site, it might take some time to get the software.
Resource | Default value | Information |
---|---|---|
MVS build procedures | ELAXF* | PROCLIB changes |
Resource | Default value | Information |
---|---|---|
IPL with CLPA | not applicable | Integrated Debugger |
started task | DBGMGR | Integrated Debugger |
LINKLIST data set | FEL.SFELAUTH and FEL.SFELLOAD | |
LPA data set | FEL.SFELLPA | |
Security profiles | AQE.** | |
port range for host-confined use | any available port is used | |
port range for host-confined use | 5336 | Integrated Debugger |
port for client-host communication |
|
|
CICS CSD update | multiple values | |
CICS JCL update |
|
Administrator | Task | Information |
---|---|---|
System | Typical system programmer actions are required for all customization tasks | N/A |
Administrator | Task | Information |
---|---|---|
System | Typical system programmer actions are required for all customization tasks | N/A |
Security | ![]()
![]() |
![]()
![]() |
TCP/IP | Define new TCP/IP ports | "TCP/IP ports" in Host Configuration Reference (SC27-8578) |
SCLM |
|
SCLM Developer Toolkit |
CICS TS |
|
|
WLM |
|
|
LDAP | Define groups for push-to-client | “Push-to-client considerations” in the Host Configuration Reference (SC27-8578) |
For information about Developer for z
Systems itself,
how it interacts with your system, and with the prerequisite and co-requisite
products, see the Rational
Developer for z Systems Host Configuration Reference Guide
(SC27-8578) . The IBM Explorer
for z/OS Host Configuration
Reference (SC27-8438) gives similar information for z/OS Explorer, which is a requisite
for Developer for z Systems.
This information can assist you in creating a setup that supports
your current needs and future growth.
Unlike traditional z/OS applications, Developer for z Systems is not a monolithic application that can be identified easily to Workload Manager (WLM). Developer for z Systems consists of several components that interact to give the client access to the host system services and data. To plan your WLM configuration, see "WLM considerations" in the Host Configuration Reference (SC27-8578) .
Developer for z Systems uses a variable number of system resources such as address spaces, and z/OS UNIX processes and threads. The availability of these resources is limited by various system definitions. To estimate the usage of key resources so that you can plan your system configuration, see "Tuning considerations" in the Host Configuration Reference (SC27-8578) . Developer for z Systems can run in either 31-bit or 64-bit mode, changing the storage resource limitations drastically.
The user ID of a Developer for z Systems user must have at least the following attributes:
USER=userid
OMVS INFORMATION
----------------
UID= 0000003200
HOME= /u/userid
PROGRAM= /bin/sh
CPUTIMEMAX= NONE
ASSIZEMAX= NONE
FILEPROCMAX= NONE
PROCUSERMAX= NONE
THREADSMAX= NONE
MMAPAREAMAX= NONE
GROUP group
OMVS INFORMATION
----------------
GID= 0000003243
Developer for z Systems supports the cloning of an installation to a different system, thus avoiding the need for a SMP/E installation on each system.
Developer for z Systems
Users of the Developer for z Systems client must know the result of certain host system 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.
Customization | Value |
---|---|
![]() This port is set during z/OS Explorer configuration.. ![]() |
Customization | Value |
---|---|
Location of the ELAXF* procedures
if they are not in a system procedure library. The default is FEL.#CUST.PROCLIB. See the note on JCLLIB in ELAXF* remote build procedures. |
|
Procedure or step names of the ELAXF* procedures
if they were changed. See the note on changing them in ELAXF* remote build procedures. |
|
Location of the AKGCR procedure
if it is not in a system procedure library. The default is AKG.#CUST.PROCLIB. See the note on JCLLIB in Code review. |
|
Location of the AKGCC procedure
if it is not in a system procedure library. The default is AKG.#CUST.PROCLIB. See the note on JCLLIB in Code coverage. |
|
Location of the FEKRNPLI Include Preprocessor exec statement. The default is FEL.#CUST.CNTL. | |
Location of the debugger load modules if not in LINKLIST. The default is FEL.SFELAUTH. See Integrated Debugger | |
Location of the unit test load modules if not in LINKLIST or STEPLIB of rdz.env. The default is FEL.SFELLOAD. | |
Location of the AZUZUNIT procedure
if it is not in a system procedure library. The default is FEL.#CUST.PROCLIB. See the note on JCLLIB in xUnit support for Enterprise COBOL and PL/I. |
|
Location of the sample *.xsd and *.xsl XML files used for unit test output formatting. The defaults are /usr/lpp/ibm/rdz/samples/zunit/xsd and /usr/lpp/ibm/rdz/samples/zunit/xsl. | |
(co-requisite) TN3270 port number for Host Connect
Emulator. The default is 23. See "TCP/IP ports" in Host Configuration Reference (SC27-8578) . |
|
(co-requisite) REXEC or SSH port number, which, by default are 512 or 22. | |
(co-requisite) Debug Tool server port number (no default). | |
Location of the SFELSAMP sample library for
CARMA RAM samples. The default is FEL.SFELSAMP. See the CARMA Developer’s Guide (SC23-7660). |
|
Location of the CRA#ASLM JCL
for CARMA SCLM RAM data set allocations. The default is FEL.#CUST.JCL. See the note on CRA#ASLM in SCLM RAM. |
The following customization steps are common for the
various Developer for z
Systems services.
See the chapters about the specific components for their customization
requirements.
Developer for z Systems contains several sample configuration files and sample JCL. To avoid overwriting your customizations when applying maintenance, copy all of these members and z/OS UNIX files to a different location, and customize the copy.
Some functions of Developer for z Systems require the existence of certain directories in z/OS UNIX, which must be created during the customization of the product. To ease the installation effort, a sample job, FELSETUP, is provided to create the copies and the required directories.
To create customizable copies of configuration files and configuration JCL, and to create required z/OS UNIX directories, customize and submit the sample FELSETUP member in the FEL.SFELSAMP data set. The required customization steps are described within the member.
mkdir /usr/lpp/ibm/rdz/cust
ln -s /usr/lpp/ibm/rdz/cust /etc/zexpl
For more information about the PARMLIB definitions listed in the next sections, see MVS Initialization and Tuning Reference (SA22-7592). For more information about the sample console commands, see MVS System Commands (SA22-7627).
SCLM Developer Toolkit starts multiple, user-owned, processes concurrently during certain user activities.
Define OMVS=xx in the IEASYSxx parmlib member to specify which BPXPRMxx parmlib member should be used during IPL.
MAXPROCUSER specifies the maximum number of processes that a single z/OS UNIX user ID can have concurrently active. Set MAXPROCUSER in SYS1.PARMLIB(BPXPRMxx) to 50 or higher. This setting is intended to be a system-wide limit, because it should be active for each client that uses Developer for z Systems.
MOUNT FILESYSTEM('#dsn')
MOUNTPOINT('-PathPrefix-usr/lpp/rdz')
MODE(RDWR) /* can be MODE(READ) */
TYPE(ZFS) PARM('AGGRGROW') /* zFS, with extents */
/* TYPE(HFS) */ /* HFS, auto. extent */
MOUNT FILESYSTEM('#dsn')
MOUNTPOINT('-PathPrefix-usr/lpp/rdzutil')
MODE(RDWR) /* can be MODE(READ) */
TYPE(ZFS) PARM('AGGRGROW') /* zFS, with extents */
/* TYPE(HFS) */ /* HFS, auto. extent */
Add start commands for the Developer for z
Systems servers
to SYS1.PARMLIB(COMMANDxx) to start them automatically at next system IPL. Define
CMD=xx in the IEASYSxx parmlib member to specify which
COMMNDxx parmlib member should be used during IPL.
The optional Integrated Debugger requires that the Developer for z Systems DBGMGR server is active on your system.
The optional Integrated Debugger requires that a Developer for z Systems supervisor call (SVC) is defined to your system.
Installation-defined SVCs are defined in SYS1.PARMLIB(IEASVCxx) and require an IPL to be activated. The related load module must be loaded in LPA at IPL time. Note however that Integrated Debugger allows you to do a dynamic installation or update using the Debug Manager started task. Define SVC=xx in the IEASYSxx parmlib member to specify which IEASVCxx parmlib member should be used during IPL.
SVCPARM 251,REPLACE,TYPE(3),EPNAME(AQESVC03) /* RDz debug */
If you purchased Developer for z Systems as part of product code 5697-CDT, IBM Enterprise COBOL Suite for z/OS, V1.1 (or later), and have not already done so for another program in product code 5697-CDT, include an entry in the IFAPRDxx parmlib member to enable the related programs. Define PROD=xx in the IEASYSxx parmlib member to specify which IFAPRDxx parmlib member should be used during IPL.
PRODUCT OWNER('IBM CORP')
NAME('IBM COBOL SUITE')
ID(5697-CDT)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME(*)
STATE(ENABLED)
PRODUCT OWNER('IBM CORP')
NAME('IBM RDZ')
ID(5724-T07)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME(*)
STATE(ENABLED)
SET PROD=xx
The optional Common Access Repository Manager (CARMA) service supports different server
startup methods for the CARMA server. The CRASTART startup method requires that the modules in the
FEL.SFELLPA load library are in the Link Pack Area (LPA).
LPA data sets are defined in SYS1.PARMLIB(LPALSTxx). Define LPA=xx in the IEASYSxx parmlib member to specify which LPALSTxx parmlib member should be used during IPL.
For the optional Debug Manager to work, the modules in the FEL.SFELAUTH and FEL.SFELLPA load libraries must be APF-authorized. Note that FEL.SFELLPA must be in STEPLIB for Debug Manager, and therefore requires explicit APF authorization.
For the optional SCLM Developer Toolkit service to work, the REXX runtime library (REXX.*.SEAGLPA) must be APF-authorized.
APF authorizations are defined in SYS1.PARMLIB(PROGxx) by default. Define PROG=xx in the IEASYSxx parmlib member to specify which PROGxx parmlib member should be used during IPL.
Load library | Load modules | Usage | STEPLIB |
---|---|---|---|
FEL.SFELAUTH | AQE* and CEE* | Integrated Debugger | ELAXFGO procedure, or CICS |
FEL.SFELLMOD | IRZ* and IIRZ* | Diagnostic IRZ messages for Enterprise Service Tools | CICS, IMS, or MVS batch |
FEL.SFELLOAD | AZU* and IAZU* | xUnit support for Enterprise COBOL and PL/I | rdz.env or MVS batch |
BWB* | SCLM Developer Toolkit | rdz.env | |
CRA* | Common Access Repository Manager (CARMA) | CRASUB* or crastart*.conf | |
ELAX* | ELAXF* remote build procedures (error feedback and include preprocessor) |
ELAXF* procedures | |
FEJB* | CICS bidirectional language support | CICS | |
FEL.SFELLPA | CRA* | Common Access Repository Manager (CARMA) | CRASRV.properties |
AQE* | Integrated Debugger | not applicable (LPA required) |
In order for the listed Developer for z Systems services to work, all modules documented in Table 7 that are related to the service must be made available either through STEPLIB or LINKLST (or LPA). Note that the SFELLMOD library is not used by Developer for z Systems itself, but by code generated by Developer for z Systems. See the STEPLIB column in Table 7 if you choose to use STEPLIB to learn where the STEPLIB (or DFHRPL for CICS) definition must be made. However, you should be aware of the following things:
LINKLIST data sets are defined in SYS1.PARMLIB(PROGxx), if your site followed IBM recommendations. Define PROG=xx in the IEASYSxx parmlib member to specify which PROGxx parmlib member should be used during IPL.
LINKLIST data sets are defined in SYS1.PARMLIB(PROGxx) by default. LPA data sets are defined in SYS1.PARMLIB(LPALSTxx).
The Developer for z Systems client has a code generation component called Enterprise Service Tools. In order for the generated code to issue diagnostic error messages, all IRZM* and IIRZ* modules in the FEL.SFELLMOD load library must be made available either through STEPLIB or LINKLIST.
LINKLIST data sets are defined in SYS1.PARMLIB(PROGxx) by default.
If you opt to use STEPLIB, you must define the libraries that are not available through LINKLIST in the STEPLIB directive of the task that executes the code (IMS or batch job). However, if one STEPLIB library is APF-authorized, then all other STEPLIB libraries must be authorized. Libraries lose their APF authorization when they are mixed with non-authorized libraries in STEPLIB.
The started task and remote build procedures listed in the following sections must reside in a system procedure library defined to your JES subsystem. In the instructions in the following sections, the IBM default procedure library, SYS1.PROCLIB, is used.
//*
//* RDz Debug Manager
//*
//DBGMGR PROC PRM=, * PRM=DEBUG TO START TRACING
// LEPRM='RPTOPTS(ON)',
// TZ='EST5EDT',
// CLIENT=5335,
// HOST=5336,
// SVC=251,
// HLQ=FEL
//*
//DBGMGR EXEC PGM=AQEZPCM,REGION=0M,TIME=NOLIMIT,
// PARM=('&LEPRM ENVAR("TZ=&TZ")/&HOST &CLIENT &SVC &PRM')
//STEPLIB DD DISP=SHR,DSN=&HLQ..SFELAUTH
// DD DISP=SHR,DSN=&HLQ..SFELLPA
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
// PEND
//*
Developer for z Systems provides sample JCL procedures that can be used for the JCL generation, remote project builds, and remote syntax check features of CICS BMS maps, IMS MFS screens, COBOL, PL/I, Assembler, and C/C++ programs. These procedures allow installations to apply their own standards, and ensure that developers use the same procedures with the same compiler options and compiler levels.
The sample procedures and their function are listed in Table 8.
Member | Purpose |
---|---|
ELAXFADT | Sample procedure for assembling and debugging High Level assembler programs. |
ELAXFASM | Sample procedure for assembling High Level assembler programs. |
ELAXFBMS | Sample procedure for creating CICS BMS object and corresponding copy, dsect, or include member. |
ELAXFCOC | Sample procedure for COBOL compiling and doing Integrated CICS translate and integrated DB2 translate. |
ELAXFCOP | Sample procedure for DB2 preprocessing of EXEC SQL statements embedded in COBOL programs. |
ELAXFCOT | Sample procedure for CICS translation for EXEC CICS statements embedded in COBOL programs. |
ELAXFCPC | Sample procedure for C compiling. |
ELAXFCPP | Sample procedure for C++ compiling. |
ELAXFCP1 | Sample procedure for COBOL compiling with SCM preprocessor statements (-INC and ++INCLUDE). |
ELAXFDCL | Sample procedure for running a program in TSO mode. |
ELAXFGO | Sample procedure for the GO step. |
ELAXFLNK | Sample procedure for linking C/C++, COBOL. PLI and High Level Assembler programs. |
ELAXFMFS | Sample procedure for creating IMS MFS screens. |
ELAXFPLP | Sample procedure for DB2 preprocessing of EXEC SQL statements embedded in PLI programs. |
ELAXFPLT | Sample procedure for doing CICS translation of EXEC CICS statements embedded in PLI programs. |
ELAXFPL1 | Sample procedure for PL/I compiling, and integrated CICS translation and integrated DB2 translation. |
ELAXFPP1 | Sample procedure for PL/I compiling with SCM preprocessor statements (-INC and ++INCLUDE). |
ELAXFSP | Sample procedure to register a stored procedure to DB2. |
ELAXFSQL | Sample procedure to invoke SQL. |
ELAXFTSO | Sample procedure for running and debugging the generated DB2 code in TSO mode. |
ELAXFUOP | Sample procedure for generating the UOPT step when building programs that run in CICS or IMS subsystems. |
The names of the procedures and the names of the steps in the procedures match the default properties that are included with the Developer for z Systems client. If the name of a procedure or the name of a step in a procedure is changed, the corresponding properties file on all of the clients must be updated. You should not change the procedure and step names.
Customize the sample build procedure members, FEL.#CUST.PROCLIB(ELAXF*), as described within the members, and copy them to SYS1.PROCLIB. Provide the correct high-level qualifiers for different product libraries, as described in Table 9.
Product | Default HLQ | Value |
---|---|---|
Developer for z Systems | FEK | |
CICS | CICSTS52.CICS | |
DB2 | DSNA11 | |
IMS | IMS | |
COBOL | IGY.V5R2M0 | |
PL/I | PLI.V4R2M0 | |
C/C++ | CBC | |
LE | CEE | |
system LINKLIB | SYS1 | |
system MACLIB | SYS1 |
Product | Default DSN | Value |
---|---|---|
Developer for z Systems - SQL samples | FEL.#CUST.SQL | |
DB2 run libraries | DSNA11.RUNLIB.LOAD |
If the ELAXF* procedures cannot be copied into a system procedure library, ask the Developer for z Systems users to add a JCLLIB card (right after the JOB card) to the job properties on the client.
//MYJOB JOB <job parameters>
//PROCS JCLLIB ORDER=(FEL.#CUST.PROCLIB)
To create the security definitions for Developer for z Systems, customize and submit the sample FELRACF and AQERACF members. The user submitting this job must have security administrator privileges, such as being RACF SPECIAL.
FELRACF and AQERACF are located in FEL.#CUST.JCL, unless you specified a different location when you customized and submitted the FEL.SFELSAMP(FELSETUP) job. For more details, see Customization setup.
The z/OS Explorer
RSE server processes (RSE daemon, RSE thread pool, and RSE server)
use the definitions in rdz.env to learn about Developer for z
Systems environment
variables..
rdz.env is located in /etc/zexpl/, unless you specified a different location when you customized and submitted the FEL.SFELSAMP(FELSETUP) job. For more details, see Customization setup. You can edit the file with the TSO OEDIT command.
See the following sample rdz.env file, which can be customized to match your system environment. Default values are provided for all variables that are not explicitly specified. The syntax of the file follows standard z/OS UNIX shell syntax rules. For example, comments start with a number sign (#) when using a US code page, and spaces around the equal sign (=) are not supported.
#RDZ_HOME=/usr/lpp/ibm/rdz
#RDZ_HLQ=FEL
## debug
#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Ddebug.miner.autoreconnect=0"
#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Ddebug.miner.localhost=localhost"
## C/C++
#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dinclude.c=/etc/zexpl/include.conf"
#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dinclude.cpp=/etc/zexpl/include.conf"
#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DCPP_CLEANUP_INTERVAL=60000"
## remote index search
#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DRIS_BUFFER=8"
#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDISABLE_REMOTE_INDEX_SEARCH=true"
## system
#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDISABLE_DELETE_IN_SUBPROJECT=true"
## zUnit unit test
#STEPLIB=$STEPLIB:$RDZ_HLQ.SFELLOAD
#STEPLIB=$STEPLIB:SYS1.CSSLIB:SYS1.SIXMLOD1
## RTC user build
#RDZ_UBLD_DD=$CGI_ISPCONF/ISPF.conf
#RDZ_UBLD_STEPLIB=$STEPLIB
## SCLM Developer Toolkit
#_SCLMDT_CONF_HOME=/var/rdz/sclmdt
#STEPLIB=$STEPLIB:$RDZ_HLQ.SFELAUTH:$RDZ_HLQ.SFELLOAD
#_SCLMDT_TRANTABLE=FEL.#CUST.LSTRANS.FILE
#ANT_HOME=/usr/lpp/Apache/Ant/apache-ant-1.7.1
The following definitions are optional. If omitted, default values are used.
debug.miner.autoreconnect | Reconnect behavior |
---|---|
-1 | Do not reconnect |
0 (default) | Attempt to reconnect every minute until successful |
1-86400 | Attempt to reconnect up to the specified amount of times. The maximum value, 86400, equals 24 hours. |
# SCLM Developer Toolkit
STEPLIB=$STEPLIB:$RSE_HLQ.SFELAUTH:$RSE_HLQ.SFELLOAD
# zUnit, xUnit support for Enterprise COBOL and PL/I
STEPLIB=$STEPLIB:$RSE_HLQ.SFELLOAD:SYS1.CSSLIB:SYS1.SIXMLOD1
Developer for z Systems consists of various unrelated features, each with their own customization tasks. Follow the instructions in the appropriate section to configure the required service.
The detailed description of the various installation
verification programs (IVPs) is located in Installation verification.
Common Access Repository Manager (CARMA) is a server 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 available for a client to access any supported SCM.
Developer for z Systems provides multiple pre-built RAMs and source code examples for creating your own RAM.
SCMs that are based on host systems need single-user address spaces to access their services, which requires CARMA to start a CARMA server for each user. It is not possible to create a single server supporting multiple users.
Developer for z Systems supports multiple methods to start a CARMA server. Developer for z Systems also provides multiple Repository Access Managers (RAMs), which can be divided into two groups, production RAMs and sample RAMs. This publication describes several possible combinations of RAMs and server startup methods. Each of the described configuration scenarios is available as a preconfigured setup.
Developer for z Systems supports multiple methods to start a CARMA server. Each method has benefits and drawbacks.
The "CRASTART" method starts the CARMA server as a subtask within RSE. This method provides a very flexible setup by using a separate configuration file that defines data set allocations and program invocations that are needed to start a CARMA server. This method provides the best performance and uses the fewest resources, but requires that the CRASTART module be located in LPA.
The "batch submit" method starts the CARMA server by submitting a job. This is the default method that is used in the provided sample configuration files. The benefit of this method is that the CARMA logs are easily accessible in the job output. It also allows the use of custom server JCL for each developer, which is maintained by the developer himself. However, this method uses one JES initiator for each developer who starts a CARMA server.
Production type RAMs are fully functional, pre-built RAMs that can be used to access an SCM in a production environment.
The IBM
Rational Developer for z Systems Interface
for CA Endevor® Software Configuration Manager gives Developer for z
Systems clients
direct access to CA Endevor® SCM.
The CA Endevor® SCM packages RAM gives Developer for z Systems clients direct access to CA Endevor® SCM packages.
Sample RAMs are provided for the purpose of testing the configuration of your CARMA environment and as examples for developing your own RAMs. Source code is included.
The PDS RAM gives a data set list similar to MVS Files -> My Data Sets in the Remote Systems view.
The skeleton RAM gives a functional framework that can be used as starting point to develop your own RAM.
The SCLM RAM gives a basic entry into SCLM, ISPF's Software Configuration Manager. The SCLM RAM is not enabled by default.
Detailed information on the different steps of each scenario can be found in CARMA configuration details.
It is possible to add a RAM to any CARMA setup, now or somewhere in the future. See (Optional) Supporting multiple RAMs for more information on adding a RAM to an existing setup.
This customization step can be omitted if you want to use one of the other scenarios with different specifications.
To define and populate the CARMA-related VSAM data sets, customize and submit the following JCL jobs. For customization instructions, see the documentation within the member. Existing VSAM data sets are replaced.
For more details on this step, see CARMA VSAM data sets.
RSE server uses the settings in /etc/zexpl/CRASRV.properties to start and connect to a CARMA server. You can edit the file with the TSO OEDIT command. For the changes to take effect, restart the RSED started task.
When you use the default file locations, the only required changes are changing the value of the clist.dsname directive to *CRASTART and changing the value of crastart.configuration.file to crastart.endevor.conf. For more information about the different directives, see CRASRV.properties, the RSE interface to CARMA.
clist.dsname=*CRASTART
crastart.configuration.file=crastart.endevor.conf
CRASTART uses the definitions in /etc/zexpl/crastart.endevor.conf to create a valid TSO/ISPF environment to start a CARMA server. You can edit the file with the TSO OEDIT command. Changes are in effect for all CARMA servers that are started after the update.
For customization instructions, see the documentation within the file. For more information about the CRASTART startup method, see crastart*.conf, the CRASTART server startup.
* DD used by RAM
TYPEMAP = FEL.#CUST.PARMLIB(CRATMAP)
SHOWVIEW= FEL.#CUST.PARMLIB(CRASHOW)
CRACFG = FEL.#CUST.PARMLIB(CRACFG)
* uncomment CRABCFG and CRABSKEL to use batch actions
*CRABCFG = FEL.#CUST.PARMLIB(CRABCFG)
*CRABSKEL= FEL.#CUST.CNTL
* uncomment and provide correct DSN to use Package Ship
*APIHJC = #shiphjc
CONLIB = CA.NDVR.CSIQLOAD
-COMMAND=ALLOC FI(JCLOUT) SYSOUT(A) WRITER(INTRDR) RECFM(F) LRECL(80)
BLKSIZE(80)
-COMMAND=ALLOC FI(EXT1ELM) NEW DELETE DSORG(PS) RECFM(V,B) LRECL(4096)
BLKSIZE(27998) SPACE(5,5) TRACKS UNIT(SYSALLDA)
-COMMAND=ALLOC FI(EXT2ELM) NEW DELETE DSORG(PS) RECFM(V,B) LRECL(4096)
BLKSIZE(27998) SPACE(5,5) TRACKS UNIT(SYSALLDA)
-COMMAND=ALLOC FI(EXT1DEP) NEW DELETE DSORG(PS) RECFM(V,B) LRECL(4096)
BLKSIZE(27998) SPACE(5,5) TRACKS UNIT(SYSALLDA)
C1EXMSGS= SYSOUT(H)
C1MSGS1 = SYSOUT(H)
MSG3FILE= DUMMY
* DD used by CARMA server (CRASERV)
* pay attention to APF authorizations when using TASKLIB
TASKLIB = FEL.SFELLOAD,CA.NDVR.CSIQAUTH,CA.NDVR.CSIQAUTU
CRADEF = FEL.#CUST.CRADEF
CRAMSG = FEL.#CUST.CRAMSG
CRASTRS = FEL.#CUST.CRASTRS
CARMALOG= SYSOUT(H)
SYSPRINT= SYSOUT(H)
* DD used by ISPF (via NDVRC1)
-COMMAND=ALLOC FI(ISPCTL0) NEW DELETE DSORG(PS) RECFM(F,B) LRECL(80)
BLKSIZE(32720) SPACE(5,5) TRACKS UNIT(SYSALLDA)
-COMMAND=ALLOC FI(ISPCTL1) NEW DELETE DSORG(PS) RECFM(F,B) LRECL(80)
BLKSIZE(32720) SPACE(5,5) TRACKS UNIT(SYSALLDA)
-COMMAND=ALLOC FI(ISPPROF) NEW DELETE DSORG(PO) RECFM(F,B) LRECL(80)
BLKSIZE(32720) SPACE(5,5) TRACKS UNIT(SYSALLDA) DIR(5)
ISPTABL = -ISPPROF
ISPTLIB = -ISPPROF,ISP.SISPTENU
ISPMLIB = ISP.SISPMENU
ISPPLIB = ISP.SISPPENU
ISPSLIB = ISP.SISPSENU
* DD used by TSO (IKJEFT01)
SYSPROC = FEL.SFELPROC * CRANDVRA
SYSTSIN = DUMMY
SYSTSPRT= SYSOUT(H)
PROGRAM=IKJEFT01 %CRANDVRA NDVRC1 PGM(CRASERV) PARM(&CRAPRM1.
&CRAPRM2. &CRAPRM3. &CRAPRM4. &CRAPRM5. &CRAPRM6. &CRAPRM7.
&CRAPRM8. )
This customization step can be bypassed if you want to use one of the other scenarios with different specifications.
Customize and submit the following JCL jobs to define and populate the CARMA-related VSAM data sets. For customization instructions, see the documentation within the member. Existing VSAM data sets are replaced.
For more details on this step, see CARMA VSAM data sets and CARMA Repository Access Managers (RAMs).
RSE server uses the settings in /etc/zexpl/CRASRV.properties to start and connect to a CARMA server. You can edit the file with the TSO OEDIT command. For the changes to take effect, the RSED started task must be restarted.
When using the default file locations, the only required change is changing the value of the clist.dsname directive to *CRASTART. For more information about the different directives, see CRASRV.properties, the RSE interface to CARMA.
clist.dsname=*CRASTART
crastart.configuration.file=crastart.conf
CRASTART uses the definitions in /etc/zexpl/crastart.conf to create a valid TSO/ISPF environment to start a CARMA server. You can edit the file with the TSO OEDIT command. Changes are in effect for all CARMA servers that are started after the update.
For customization instructions, see the documentation within the file. For more information about the CRASTART startup method, see crastart*.conf, the CRASTART server startup.
* DD used by RAM
CRARAM1 = FEL.#CUST.CRARAM1 * PDS RAM
* DD used by CARMA server (CRASERV)
TASKLIB = FEL.SFELLOAD
CRADEF = FEL.#CUST.CRADEF
CRAMSG = FEL.#CUST.CRAMSG
CRASTRS = FEL.#CUST.CRASTRS
CARMALOG= SYSOUT(H)
SYSPRINT= SYSOUT(H)
* DD used by ISPF (ISPSTART)
-COMMAND=ALLOC FI(ISPCTL0) NEW DELETE DSORG(PS) RECFM(F,B) LRECL(80)
BLKSIZE(32720) SPACE(5,5) TRACKS UNIT(SYSALLDA)
-COMMAND=ALLOC FI(ISPCTL1) NEW DELETE DSORG(PS) RECFM(F,B) LRECL(80)
BLKSIZE(32720) SPACE(5,5) TRACKS UNIT(SYSALLDA)
-COMMAND=ALLOC FI(ISPPROF) NEW DELETE DSORG(PO) RECFM(F,B) LRECL(80)
BLKSIZE(32720) SPACE(5,5) TRACKS UNIT(SYSALLDA) DIR(5)
ISPTABL = -ISPPROF
ISPTLIB = -ISPPROF,ISP.SISPTENU
ISPMLIB = ISP.SISPMENU
ISPPLIB = ISP.SISPPENU
ISPSLIB = ISP.SISPSENU
* DD used by TSO (IKJEFT01)
SYSPROC = #hlq.SFELPROC * CRAALLOC
SYSTSIN = DUMMY
SYSTSPRT= SYSOUT(H)
PROGRAM=IKJEFT01 %CRAALLOC ISPSTART PGM(CRASERV) PARM(&CRAPRM1.
&CRAPRM2. &CRAPRM3. &CRAPRM4. &CRAPRM5. &CRAPRM6. &CRAPRM7.
&CRAPRM8. )
The custom RAMs have additional components that can be customized if needed.
This customization step can be omitted if you want to use one of the other scenarios with different specifications.
Customize and submit the following JCLs to define and populate the CARMA-related VSAM data sets. For customization instructions, see the documentation within the member. Existing VSAM data sets are replaced.
For more details on this step, see CARMA VSAM data sets.
RSE server uses the settings in /etc/zexpl/CRASRV.properties to start and connect to a CARMA server. You can edit the file with the TSO OEDIT command. For the changes to take effect, the RSED started task must be restarted.
When using default file locations, the only required change is changing the value of the clist.dsname directive to FEL.#CUST.CNTL(CRASUBCA). For more information about the different directives, see CRASRV.properties, the RSE interface to CARMA.
clist.dsname='FEL.#CUST.CNTL(CRASUBCA)'
The FEL.#CUST.CNTL(CRASUBCA) CLIST and embedded JCL submits a CARMA server. Changes are in effect for all CARMA servers that are started after the update.
For customization instructions, see the documentation within the member. For more information about the batch submit startup method, see CRASUB*, the batch submit server startup.
PROC 8 CRAPRM1 CRAPRM2 CRAPRM3 CRAPRM4 CRAPRM5 CRAPRM6 CRAPRM7 CRAPRM8
SUBMIT * END($$)
//CRA&PORT JOB CLASS=A,MSGCLASS=A,MSGLEVEL=(1,1)
//*
//RUN EXEC PGM=IKJEFT01,DYNAMNBR=125,REGION=0M,TIME=NOLIMIT
//*
//* DD used by RAM
//TYPEMAP DD DISP=SHR,DSN=FEL.#CUST.PARMLIB(CRATMAP)
//SHOWVIEW DD DISP=SHR,DSN=FEL.#CUST.PARMLIB(CRASHOW)
//CRACFG DD DISP=SHR,DSN=FEL.#CUST.PARMLIB(CRACFG)
//* uncomment CRABCFG and CRABSKEL to use batch actions
//*CRABCFG DD DISP=SHR,DSN=FEL.#CUST.PARMLIB(CRABCFG)
//*CRABSKEL DD DISP=SHR,DSN=FEL.#CUST.CNTL
//* uncomment and provide correct DSN to use Package Ship
//*APIHJC DD DISP=SHR,DSN=#shiphjc
//CONLIB DD DISP=SHR,DSN=CA.NDVR.CSIQLOAD
//JCLOUT DD SYSOUT=(A,INTRDR),DCB=(LRECL=80,RECFM=F,BLKSIZE=80)
//EXT1ELM DD DISP=(NEW,DELETE),UNIT=SYSALLDA,
// RECFM=VB,LRECL=4096,BLKSIZE=27998,SPACE=(TRK,(5,5))
//EXT2ELM DD DISP=(NEW,DELETE),UNIT=SYSALLDA,
// RECFM=VB,LRECL=4096,BLKSIZE=27998,SPACE=(TRK,(5,5))
//EXT1DEP DD DISP=(NEW,DELETE),UNIT=SYSALLDA,
// RECFM=VB,LRECL=4096,BLKSIZE=27998,SPACE=(TRK,(5,5))
//C1MSGS1 DD SYSOUT(H)
//C1EXMSGS DD SYSOUT(H)
//MSG3FILE DD DUMMY
//*
//* DD used by CARMA server (CRASERV)
//* pay attention to APF authorizations when using STEPLIB
//STEPLIB DD DISP=SHR,DSN=FEL.SFELLOAD
// DD DISP=SHR,DSN=CA.NDVR.CSIQAUTH
// DD DISP=SHR,DSN=CA.NDVR.CSIQAUTU
//CRADEF DD DISP=SHR,DSN=FEL.#CUST.CRADEF
//CRAMSG DD DISP=SHR,DSN=FEL.#CUST.CRAMSG
//CRASTRS DD DISP=SHR,DSN=FEL.#CUST.CRASTRS
//CARMALOG DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//*
//* DD used by ISPF (via NDVRC1)
//ISPPROF DD DISP=(NEW,DELETE,DELETE),UNIT=SYSALLDA,
// LRECL=80,RECFM=FB,SPACE=(TRK,(1,1,5))
//ISPCTL0 DD DISP=(NEW,DELETE,DELETE),UNIT=SYSALLDA,
// LRECL=80,RECFM=FB,SPACE=(TRK,(5,5))
//ISPCTL1 DD DISP=(NEW,DELETE,DELETE),UNIT=SYSALLDA,
// LRECL=80,RECFM=FB,SPACE=(TRK,(5,5))
//ISPMLIB DD DISP=SHR,DSN=ISP.SISPMENU
//ISPPLIB DD DISP=SHR,DSN=ISP.SISPPENU
//ISPSLIB DD DISP=SHR,DSN=ISP.SISPSENU
//ISPTLIB DD DISP=SHR,DSN=ISP.SISPTENU
//*
//* DD used by TSO (IKJEFT01)
//SYSPROC DD DISP=SHR,DSN=FEL.SFELPROC * CRANDVRA
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
%CRANDVRA NDVRC1 PGM(CRASERV) PARM(&CRAPRM1 &CRAPRM2 &STR(+)
&CRAPRM3 &STR(+)
&CRAPRM4 &STR(+)
&CRAPRM5 &STR(+)
&CRAPRM6 &STR(+)
&CRAPRM7 &STR(+)
&CRAPRM8 &STR(+) )
$$
EXIT CODE(0)
This customization step can be omitted if you want to use one of the other scenarios with different specifications.
Customize and submit the following JCL jobs to define and populate the CARMA-related VSAM data sets. For customization instructions, see the documentation within the member. Existing VSAM data sets are replaced.
For more details on this step, see CARMA VSAM data sets and CARMA Repository Access Managers (RAMs).
RSE server uses the settings in /etc/zexpl/CRASRV.properties to start and connect to a CARMA server. You can edit the file with the TSO OEDIT command. For the changes to take effect, the RSED started task must be restarted.
When using default file locations, the only required change is changing the value of
the clist.dsname directive to FEL.#CUST.CNTL(CRASUBMT). For more information about
the different directives, see CRASRV.properties, the RSE interface to CARMA.
clist.dsname='FEL.#CUST.CNTL(CRASUBMT)'
The FEL.#CUST.CNTL(CRASUBMT) CLIST and embedded JCL submits a CARMA server. Changes are in effect for all CARMA servers that are started after the update.
For customization instructions, see the documentation within the member. For more information about the batch submit startup method, see CRASUB*, the batch submit server startup.
PROC 8 CRAPRM1 CRAPRM2 CRAPRM3 CRAPRM4 CRAPRM5 CRAPRM6 CRAPRM7 CRAPRM8
SUBMIT * END($$)
//CRA&PORT JOB CLASS=A,MSGCLASS=A,MSGLEVEL=(1,1)
//*
//RUN EXEC PGM=IKJEFT01,DYNAMNBR=125,REGION=0M,TIME=NOLIMIT
//*
//* DD used by RAM
//CRARAM1 DD DISP=SHR,DSN=FEL.#CUST.CRARAM1 * PDS RAM
//*
//* DD used by CARMA server (CRASERV)
//STEPLIB DD DISP=SHR,DSN=FEL.SFELLOAD
//CRADEF DD DISP=SHR,DSN=FEL.#CUST.CRADEF
//CRAMSG DD DISP=SHR,DSN=FEL.#CUST.CRAMSG
//CRASTRS DD DISP=SHR,DSN=FEL.#CUST.CRASTRS
//CARMALOG DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//*
//* DD used by ISPF (ISPSTART)
//ISPPROF DD DISP=(NEW,DELETE,DELETE),UNIT=SYSALLDA,
// LRECL=80,RECFM=FB,SPACE=(TRK,(1,1,5))
//ISPCTL0 DD DISP=(NEW,DELETE,DELETE),UNIT=SYSALLDA,
// LRECL=80,RECFM=FB,SPACE=(TRK,(5,5))
//ISPCTL1 DD DISP=(NEW,DELETE,DELETE),UNIT=SYSALLDA,
// LRECL=80,RECFM=FB,SPACE=(TRK,(5,5))
//ISPMLIB DD DISP=SHR,DSN=ISP.SISPMENU
//ISPPLIB DD DISP=SHR,DSN=ISP.SISPPENU
//ISPSLIB DD DISP=SHR,DSN=ISP.SISPSENU
//ISPTLIB DD DISP=SHR,DSN=ISP.SISPTENU
//*
//* DD used by TSO (IKJEFT01)
//SYSPROC DD DISP=SHR,DSN=#hlq.SFELPROC * CRAALLOC
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
%CRAALLOC ISPSTART PGM(CRASERV) PARM(&CRAPRM1 &CRAPRM2 &STR(+)
&CRAPRM3 &STR(+)
&CRAPRM4 &STR(+)
&CRAPRM5 &STR(+)
&CRAPRM6 &STR(+)
&CRAPRM7 &STR(+)
&CRAPRM8 &STR(+)
)
$$
EXIT CODE(0)
The custom RAMs have additional components that can be customized if needed.
The different configuration scenarios that are documented in this publication share many of the CARMA configuration files. The details of these configuration files are documented here, and they are referenced from within the various scenarios.
The CARMA server provides a standard API for other products that use host systems to access one or more Software Configuration Managers (SCMs). However, it does not provide methods for direct communication with a client computer. For this communication, it relies on other products, such as the RSE server. The RSE server uses the settings in CRASRV.properties to start and connect to a CARMA server.
# CRASRV.properties - CARMA configuration options
#
clist.dsname=''
crastart.configuration.file=crastart.conf
#port.start=0
#port.range=100
#user.exit='FEL.SFELSAMP(CRAEXIT)'
#startup.script.name=carma.startup.rex
#crastart.stub=CRASTART
#crastart.syslog=Partial
#crastart.timeout=420
#crastart.steplib=FEL.SFELLPA
#crastart.tasklib=TASKLIB
The default is a null string, to indicate that CARMA is not configured.
With quotes (') the data set name is an absolute reference, without quotes (') the data set name is prefixed with the client's user ID, not the TSO prefix. The latter requires that all CARMA users must maintain their own exit code.
A sample user exit is provided as FEL.SFELSAMP(CRAEXIT). This sample also documents the startup arguments passed to the user exit. For more information see (Optional) CARMA user exit.
A (All) | All tracing information is printed to SYSLOG |
P (Partial) | Only connect, disconnect, and error information is printed to SYSLOG |
anything else | Only error conditions are printed to SYSLOG |
To specify the required detail level for system log messages, uncomment and customize. This directive is used only if the clist.dsname directive has *CRASTART as value.
RSE starts the CRASTART load module, which uses the definitions in crastart*.conf to create a valid environment to execute batch TSO and ISPF commands. Rational Developer for z Systems uses this environment to run the CARMA server, CRASERV.
crastart*.conf is located in /etc/zexpl/, unless you specified a different location when you customized and submitted job FEL.SFELSAMP(FELSETUP). For more details, see Customization setup. You can edit the file with the TSO OEDIT command.
&CRAUSER. | Client user ID |
&CRADATE. | Current® date in Dyyyyddd format (7 char Julian) |
&CRATIME. | Current time in Thhmmss format (hour min sec) |
&CRAPRM1. | Port number |
System symbol | Any SYS1.PARMLIB(IEASYMxx) system symbol |
-<ddname> | A hyphen (-) followed by a previously defined DD name acts like a *.ddname backward reference in JCL. The original DD must be allocated using the –COMMAND statement. |
Figure 12 shows a basic crastart*.conf skeleton that includes ISPF services.
* DD used by RAM
* DD used by CARMA server (CRASERV)
TASKLIB = FEL.SFELLOAD
CRADEF = FEL.#CUST.CRADEF
CRAMSG = FEL.#CUST.CRAMSG
CRASTRS = FEL.#CUST.CRASTRS
CARMALOG= SYSOUT(H)
SYSPRINT= SYSOUT(H)
* DD used by ISPF (ISPSTART)
-COMMAND=ALLOC FI(ISPCTL0) NEW DELETE DSORG(PS) RECFM(F,B) LRECL(80)
BLKSIZE(32720) SPACE(5,5) TRACKS UNIT(SYSALLDA)
-COMMAND=ALLOC FI(ISPCTL1) NEW DELETE DSORG(PS) RECFM(F,B) LRECL(80)
BLKSIZE(32720) SPACE(5,5) TRACKS UNIT(SYSALLDA)
-COMMAND=ALLOC FI(ISPPROF) NEW DELETE DSORG(PO) RECFM(F,B) LRECL(80)
BLKSIZE(32720) SPACE(5,5) TRACKS UNIT(SYSALLDA) DIR(5)
ISPTABL = -ISPPROF
ISPTLIB = -ISPPROF,ISP.SISPTENU
ISPMLIB = ISP.SISPMENU
ISPPLIB = ISP.SISPPENU
ISPSLIB = ISP.SISPSENU
* DD used by TSO (IKJEFT01)
SYSPROC = #hlq.SFELPROC * CRAALLOC
SYSTSIN = DUMMY
SYSTSPRT= SYSOUT(H)
PROGRAM=IKJEFT01 %CRAALLOC ISPSTART PGM(CRASERV) PARM(&CRAPRM1.
&CRAPRM2. &CRAPRM3. &CRAPRM4. &CRAPRM5. &CRAPRM6. &CRAPRM7.
&CRAPRM8. )
CRASTART creates a TSO environment as a child process of RSE, which runs in a separate address space. Non-trivial actions might be needed to keep the CARMA output sent to SYSOUT(*), which complicates the collecting of log files. This difficulty can be resolved by writing the log files to a user-specific data set, as shown in the following sample allocation:
-COMMAND=ALLOC FI(CARMALOG) MOD CATALOG DSORG(PS) RECFM(F,B) LRECL(133)
BLKSIZE(27930) SPACE(5,5) TRACKS UNIT(SYSALLDA)
DA(&CRAUSER..&SYSNAME..CRA.CARMALOG)
RSE starts CLIST CRASUB*, which in turn submits an embedded JCL to create a valid environment to execute batch TSO and ISPF commands. Rational Developer for z Systems uses this environment to run the CARMA server, CRASERV.
CRASUB* is located in FEL.#CUST.CNTL, unless you specified a different location when you customized and submitted the FEL.SFELSAMP(FELSETUP) job. For more details, see Customization setup.
Figure 13 shows a basic CRASUB* skeleton that includes ISPF services.
PROC 8 CRAPRM1 CRAPRM2 CRAPRM3 CRAPRM4 CRAPRM5 CRAPRM6 CRAPRM7 CRAPRM8
/* SET CRAPRM2=420
SUBMIT * END($$)
//CRA&PORT JOB CLASS=A,MSGCLASS=A,MSGLEVEL=(1,1)
//*
//RUN EXEC PGM=IKJEFT01,DYNAMNBR=125,REGION=0M,TIME=NOLIMIT
//*
//* DD used by RAM
//*
//* DD used by CARMA server (CRASERV)
//STEPLIB DD DISP=SHR,DSN=FEL.SFELLOAD
//CRADEF DD DISP=SHR,DSN=FEL.#CUST.CRADEF
//CRAMSG DD DISP=SHR,DSN=FEL.#CUST.CRAMSG
//CRASTRS DD DISP=SHR,DSN=FEL.#CUST.CRASTRS
//CARMALOG DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//*
//* DD used by ISPF (ISPSTART)
//ISPPROF DD DISP=(NEW,DELETE,DELETE),UNIT=SYSALLDA,
// LRECL=80,RECFM=FB,SPACE=(TRK,(1,1,5))
//ISPCTL0 DD DISP=(NEW,DELETE,DELETE),UNIT=SYSALLDA,
// LRECL=80,RECFM=FB,SPACE=(TRK,(5,5))
//ISPCTL1 DD DISP=(NEW,DELETE,DELETE),UNIT=SYSALLDA,
// LRECL=80,RECFM=FB,SPACE=(TRK,(5,5))
//ISPMLIB DD DISP=SHR,DSN=ISP.SISPMENU
//ISPPLIB DD DISP=SHR,DSN=ISP.SISPPENU
//ISPSLIB DD DISP=SHR,DSN=ISP.SISPSENU
//ISPTLIB DD DISP=SHR,DSN=ISP.SISPTENU
//*
//* DD used by TSO (IKJEFT01)
//SYSPROC DD DISP=SHR,DSN=#FEL.SFELPROC * CRAALLOC
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
%CRAALLOC ISPSTART PGM(CRASERV) PARM(&CRAPRM1 &CRAPRM2 &STR(+)
&CRAPRM3 &STR(+)
&CRAPRM4 &STR(+)
&CRAPRM5 &STR(+)
&CRAPRM6 &STR(+)
&CRAPRM7 &STR(+)
&CRAPRM8 &STR(+)
)
$$
EXIT CODE(0)
The CARMA server requires READ access to three VSAM data sets. The sample members to create and populate these VSAM data sets are located in FEL.#CUST.JCL, unless you specified a different location when you customized and submitted the FEL.SFELSAMP(FELSETUP) job. For more details, see Customization setup.
The mentioned sample jobs can be used to disable a defined RAM during VSAM creation. Doing so enables you to create a customized CARMA setup by using a single master input file, which can be one provided by IBM or customized by your RAM developers.
A Repository Access Manager (RAM) is an Application Programming Interface (API) for a z/OS based Software Configuration Manager (SCM). In turn, Developer for z Systems or user-written applications can start a CARMA server, which loads the RAMs and provides a standard interface to access any supported SCM.
The CARMA server must be able to find the RAM load modules, either through LINKLIST or STEPLIB/TASKLIB.
The CRAR* RAM load modules that are provided by Developer for z Systems are located in FEL.SFELLOAD, and the sample source code and compile jobs are located in FEL.SFELSAMP, unless you used a different high level qualifier during the SMP/E install of Developer for z Systems.
The following sections have customization notes for the RAMs that are available with Developer for z Systems. The referenced sample members are located in FEL.#CUST.*, unless you specified a different location when you customized and submitted the FEL.SFELSAMP(FELSETUP) sample job. For more details, see Customization setup.
For in-depth knowledge of CARMA and for more information on the sample RAMs and sample source code provided, see Common Access Repository Manager Developer's Guide (SC23-7660).
The following CA Endevor® SCM RAM-specific CARMA components can be customized, regardless of the chosen server startup method. The sample members referenced below are located in FEL.#CUST.PARMLIB, unless you specified a different location when you customized and submitted the FEL.SFELSAMP(FELSETUP) job. For more details, see Customization setup.
CRACFG specifies how the CA Endevor® SCM RAM interacts with CA Endevor® SCM. Refer to the documentation within the member for customization instructions if you want to change the defaults.
# ENTRY-STAGE-COPY-MODE = RETRIEVE-ADD
# ALTERNATIVE-ALLOC = YES
# PACKAGE-EDITING-OPTION = {READONLY | DISABLED}
# SCL-REQUIRED = YES
# SCL-DATASET-TEMPLATE = FEL.#CUST.PARMLIB(CRASCL)
# DYNAMIC-VB-DATASET-ALLOC = YES
# DATASET-ALLOC-OVERRIDE = SPACE(5,30) TRACK UNIT(SYSALLDA)
CRASCL is a template SCL (Software Control Language) that can limit which actions and options are allowed when CA Endevor® SCM Packages are processed.
When used, only actions and options explicitly listed in the template SCL are allowed to be specified in the Developer for z Systems Packages Editor. Refer to the documentation within the member for customization instructions if you want to change the defaults.
CRASHOW defines default filters for CA Endevor® SCM environments, systems, and so forth. Refer to the documentation within the member for customization instructions if you want to change the defaults.
ENV=*
TOENV=
STGID=*
TOSTGID=
SYS=*
SUBSYS=*
ELEM=*
TOELEM=
TYPE=*
#FILTER-DEP=YES
CRATMAP overrides the CA Endevor® SCM type to file extension mappings. If you want to change the defaults, see the customization instructions in the documentation within the member.
# * = cbl
# COBOL = cbl
# COPY = cpy
# ASM = asm
# MACRO = asm
# PROCESS = jcl
The following CA Endevor® SCM RAM-specific CARMA components can be customized, regardless of the chosen server startup method.
You can customize a copy of these allocation REXX execs if certain defaults, such as the data set name, do not match your site standards. The execs are located in FEL.SFELPROC, unless you used a different high-level qualifier during the SMP/E install of Developer for z Systems.
Both the batch submit and the CRASTART startup method call the CRANDVRA REXX exec to allocate user-specific data sets used by CA Endevor® SCM RAM. The allocations are done in a separate exec, because an exec allows more flexibility than what is possible within the batch submit CRASUBCA JCL and the CRASTART crastart.endevor.conf configuration file. The allocation exec is also responsible for calling the optional user exit.
DD | Data set name | Type |
---|---|---|
DEPEND | &SYSPREF..&SYSUID..&SYSNAME..CRA$NDVR.DEPEND | Permanent |
BROWSE | &SYSPREF..&SYSUID..&SYSNAME..CRA$NDVR.BROWSE | Temporary |
BROWSEV | &SYSPREF..&SYSUID..&SYSNAME..CRA$NDVR.BROWSEV | Temporary |
ENHCEDIT | &SYSPREF..&SYSUID..&SYSNAME..CRA$NDVR.ENHCEDIT | Temporary |
ENHCEDITV | &SYSPREF..&SYSUID..&SYSNAME..CRA$NDVR.ENHCEDITV | Temporary |
C1PRINT | &SYSPREF..&SYSUID..&SYSNAME..CRA$NDVR.LISTING | Temporary |
SPCLLIST | &SYSPREF..&SYSUID..&SYSNAME..CRA$NDVR.SPCLLIST | Temporary |
PKGSCLS | &SYSPREF..&SYSUID..&SYSNAME..CRA$NDVR.PKGSCLS | Temporary |
CRABJCLO | &SYSPREF..&SYSUID..&SYSNAME..CRA$NDVR.CRABJCLO | Temporary |
CRAPARM | &SYSPREF..&SYSUID..&SYSNAME..CRA$NDVR.CRAPARM | Temporary |
CA Endevor® SCM can work with variable blocked data sets with various record lengths, and requires that Developer for z Systems uses identical allocations for certain actions. Both the batch submit and the CRASTART startup method call the CRADYNDA REXX exec to allocate a work data set with the correct attributes.
Normally, CA Endevor® SCM actions such as “Generate Element” are executed “online”, in the CARMA server address space. This behavior causes problems if your CA Endevor® SCM procedures call TSO, because TSO is already active and that means that the required DDs such as SYSTSIN and SYSTSPRT are in use.
To resolve this problem, the CA Endevor® SCM RAM supports “batch actions”. When batch-actions is enabled, the CA Endevor® SCM RAM submits a customizable batch job to perform actions like “Generate Element”. Using a batch job results in the allocation of DDs such as SYSTSIN and SYSTSPRT by your CA Endevor® SCM procedures, because the submitted JCL does not require TSO to be active.
CA Endevor® SCM RAM batch-actions are the Developer for z Systems equivalent of background CA Endevor® SCM actions.
When a request is issued to execute an action that is supported by batch-actions, the CA Endevor® SCM RAM checks for the existence of the CRABCFG DD, in CRASUBCA or crastart.endevor.conf, and checks that the setup behind this DD is valid. If CRABCFG exists and the setup is valid, the action is performed in batch. If CRABCFG does not exist, the action is performed online. Developer for z Systems clients have the facility to override this behavior.
//* uncomment CRABCFG and CRABSKEL to use batch actions
//*CRABCFG DD DISP=SHR,DSN=FEL.#CUST.PARMLIB(CRABCFG)
//*CRABSKEL DD DISP=SHR,DSN=FEL.#CUST.CNTL
CRABCFG defines the configuration variables related to CA Endevor® SCM RAM batch-actions.
CRABCFG is located in FEL.#CUST.PARMLIB, unless you specified a different location when you customized and submitted the FEL.SFELSAMP(FELSETUP) job. For more details, see Customization setup.
See the following CRABCFG sample file, which must be customized to match your system environment. Comment lines start with a number sign (#) when using a US code page. Comments behind a directive and its assigned value are supported. Spaces around the equal sign (=) are supported. Line continuations are not supported.
# Location of batch action JCL
SKELETON-DD = CRABSKEL
#
# batch action JCL members within SKELETON-DD
DEFAULT-JOBCARD = CRABJOBC
ADD-ELEMENT = CRABATCA
DELETE-ELEMENT = CRABATCA
GENERATE-ELEMENT = CRABATCA
MOVE-ELEMENT = CRABATCA
RETRIEVE-ELEMENT = CRABATCA
PRINT-ELEMENT = CRABATCA
PRINT-MEMBER = CRABATCA
SIGNIN-ELEMENT = CRABATCA
TRANSFER-ELEMENT = CRABATCA
#
# Command substitution key within batch action JCL
BSTIPT01-KEY = <CRA_BSTIPT01>
CRABATCA is a sample skeleton JCL used for batch-actions. To change the defaults, see the customization instructions in the documentation within the member.
CRABATCA is located in FEL.#CUST.CNTL, unless you specified a different location when you customized and submitted the FEL.SFELSAMP(FELSETUP) job. For more details, see Customization setup.
Changes are active for all new invocations. No server restart is needed.
//<JOBCARD>
//*
//CRABATCA EXEC PGM=NDVRC1,DYNAMNBR=1500,REGION=4096K,PARM='C1BM3000'
//STEPLIB DD DISP=SHR,DSN=CA.NDVR.CSIQAUTU
// DD DISP=SHR,DSN=CA.NDVR.CSIQAUTH
//CONLIB DD DISP=SHR,DSN=CA.NDVR.CSIQLOAD
//C1MSGS1 DD SYSOUT=*
//C1MSGS2 DD SYSOUT=*
//C1PRINT DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=133)
//SYSOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYMDUMP DD DUMMY
//SYSIN DD DUMMY
//BSTIPT01 DD *
SET STOPRC 16 .
<CRA_BSTIPT01>
//*
CRABJOBC is a sample default JOB card used for batch-action skeleton JCL that specifies the <JOBCARD> key. To change the defaults, see customization instructions in the documentation within the member.
CRABJOBC is located in FEL.#CUST.CNTL, unless you specified a different location when you customized and submitted the FEL.SFELSAMP(FELSETUP) job. For more details, see Customization setup.
Changes are active for all new invocations. No server restart is needed.
//<USERID>B JOB CLASS=A,MSGCLASS=A,MSGLEVEL=(1,1)
//*PROCS JCLLIB ORDER=(COBOL.V5R1M0.SIGYPROC,CBC.SCCNPRC)
Both the batch submit and the CRASTART startup method call the CRAALLOC REXX exec to allocate user-specific data sets that can be used by a user-written RAM. The allocations are done in a separate exec, because an exec allows more flexibility than what is possible within the batch submit CRASUBMT JCL and the CRASTART crastart.conf configuration file. The allocation exec is also responsible for calling the optional user exit.
DD | Data set name | Type |
---|---|---|
CRAPARM | &SYSPREF..&SYSUID..&SYSNAME..CRA$CUST.CRAPARM | Temporary |
You can customize a copy of this allocation REXX exec if certain defaults, such as the data set name, do not match your site standards. CRAALLOC is located in FEL.SFELPROC, unless you used a different high-level qualifier during the SMP/E install of Rational Developer for z Systems.
CARMA can report various error codes to the client or in the host system logs. The details that are provided with the error, and the information in Table 12, can help you locate the error and work towards a resolution.
Error range | Error type |
---|---|
4-99 | Generic CARMA errors |
100-199 | Generic RAM errors |
200-399 | CRASERV (CARMA server) errors |
400-499 | RSE (CARMA miner) errors |
500-899 | RAM-specific errors |
900-999 | TSO and TCP/IP errors |
CARMA has the facility for defining multiple RAMs and running them concurrently. However, because there is only one CARMA server active for a user, even when there are multiple RAMs, some configuration changes might be required to make this setup work.
RAMs are defined by a RAM developer in the CARMA configuration VSAM data set, CRADEF. During startup, the CARMA server, CRASERV, identifies all of the defined RAMs and sends the information to the CARMA client. The user can then select one or more RAMs, which is loaded into the CARMA server.
Because RAMs are active as plug-ins of the CARMA server, ensure that all prerequisites, such as data set allocations, for each of the RAMs are available in the address space of the CARMA server. This requirement might need changes to the CARMA configuration samples, such as CRASUBMT or crastart.conf, which are included with Developer for z Systems.
In the following example, you start from an existing setup with the CA Endevor® SCM RAM, using the CRASTART startup method, and add the sample PDS RAM.
CRARAM1 = FEL.#CUST.CRARAM1
PROGRAM=IKJEFT01 %CRANDVRA NDVRC1 PGM(CRASERV)
PARM(&CRAPRM1. &CRAPRM2.)
The CA Endevor® SCM RAM is active in an ISPF environment, which implies that the TSO environment required by the PDS RAM is also available.
All CARMA server startup methods have limitations regarding data set allocation. For example, TSO prefix substitution is not available in JCL or CRASTART.
However, by creating an exec that is called after TSO or ISPF starts, and before CARMA is started, you can use the whole range of variables and services available in TSO or ISPF to do the required allocations.
Rational Developer for z Systems uses an allocation exec in each of the pre-configured setups described earlier in this chapter. FEL.SFELPROC(CRANDVRA), the allocation exec for CA Endevor® SCM RAM and FEL.SFELPROC(CRAALLOC), the allocation exec for custom RAMs, The exec allocates cataloged temporary data sets that have the user’s TSO prefix as high-level qualifier. The allocation exec is also responsible for calling the optional user exit.
Customization instructions are documented within the exec. Changing the allocation exec is supported, but not advised, as customizations must be redone when PTF service updates the exec. If possible, use the CARMA user exit instead, which is described in (Optional) CARMA user exit.
The following samples show how to start an allocation exec that requires only TSO.
SYSPROC = my.exec.library
PROGRAM = IKJEFT01 %myexec ISPSTART PGM(CRASERV) PARM(&CRAPRM1. &CRAPRM2. )
//SYSPROC DD DISP=SHR,DSN=my.exec.library
//SYSTSIN DD *
%myexec ISPSTART PGM(CRASERV) PARM(&CRAPRM1. &CRAPRM2. )
//*
CARMA supports the invocation of a user exit to allow for specialized initialization during startup and specialized cleanup during shutdown of the CARMA server. The usage of a user exit reduces the need to alter the allocation exec, which is maintained by PTF service.
The user exit is invoked by the allocation exec, and is executed twice. The initialization invocation is after the allocation of the temporary data sets and before the CARMA server is invoked. The cleanup invocation is after the CARMA server ended and before the temporary files are removed. If the first invocation ends with return code 99 or higher, CARMA startup is interrupted. This implies that neither CARMA server nor the second invocation of this user exit is executed.
A sample user exit is provided as FEL.SFELSAMP(CRAEXIT), unless you used a different high-level qualifier during the SMP/E install of Developer for z Systems. This sample user exit documents in detail the startup arguments passed to the user exit:
Startup argument | Description |
---|---|
(STARTUP) | (ENDING) | Indicator whether the exit invocation is before or after CARMA server invocation. |
EXIT_RC=rc | Return code of the previous invocation of the
exit. rc Is always 0 during (STARTUP) invocation. |
CARMA_RC=rc | Return code of the invocation of CARMA server. rc Is always 0 during (STARTUP) invocation. |
… | CARMA server startup command and startup arguments. For example ISPSTART PGM(CRASERV) PARM(1312 420 EXIT=CRAEXIT CLIENT=9.0.1 . . . . ) |
Output generated by the user exit is shown in DD SYSTSPRT of the CARMA server.
If the CARMA server is started using TSO (IKJEFTxx), problems might occur if your RAMs call services which in turn call the IRXJCL REXX batch interface. The problem can occur when the processors called by the RAM previously ran either without TSO, or only in online TSO, and dynamically allocates DD SYSTSIN or SYSTSPRT. A sample program, CRAXJCL, is provided to work around this problem.
Your processor might fail if it attempts to allocate SYSTSIN or SYSTSPRT, which is required for IRXJCL, because batch TSO required for CARMA already has those DD names allocated and open. The CRAXJCL replacement module attempts to allocate SYSTSIN and SYSTSPRT to DUMMY but ignores the errors which occur if the allocations fail. It then calls IRXJCL to do the actual work.
This means that when your processors run in a CARMA environment started by TSO, the allocations to SYSTSIN and SYSTSPRT are the same as those used by CARMA. When the processors are run outside of TSO/CARMA, the SYSTSIN and SYSTSPRINT allocations are created by CRAXJCL. Therefore, your processors must not rely on the contents of the data set allocated to SYSTSIN.
It is assumed that calls to IRXJCL use the PARM field to pass the REXX name and startup parameters, as documented in TSO/E REXX Reference (SA22-7790). This means that SYSTSIN can safely be used by CARMA. Any output sent to SYSTSPRT by IRXJCL is written in CARMA’s log.
Processors that call the CRAXJCL replacement module should not attempt to allocate DD SYSTSIN or SYSTSPRT before calling CRAXJCL.
The CRAXJCL replacement module is provided in source format because you must customize it to specify the specific allocations to use for SYSTSPRT. The allocation for SYSTSIN should usually be to a dummy data set.
Sample assembler source code and a sample compile/bind job are available as FEL.#CUST.ASM(CRAXJCL) and FEL.#CUST.JCL(CRA#CIRX), unless you specified a different location when you customized and submitted FEL.SFELSAMP(FELSETUP) job. For more details, see Customization setup.
Customize the CRAXJCL assembler source code as needed, using the documentation within the member. Afterward, customize and submit the CRA#CIRX JCL to create the CRAXJCL load module. For customization instructions, see the documentation within the member.
If needed, you can rename IRXJCL to something else. Adjust the CRAXJCL source to call this new name for IRXJCL and compile it, and then rename the CRAXJCL load module to IRXJCL. This setup might be easier than changing all your calls to IRXJCL.
SCLM Developer Toolkit provides the tools that are needed to extend the capabilities of SCLM to the client. SCLM itself is a host system-based source code manager that is included as part of ISPF.
The SCLM Developer Toolkit has an Eclipse-based plug-in that interfaces to SCLM and provides for access to all SCLM processes for heritage code development and support for full Java and Java EE development on the workstation with synchronization to SCLM on the mainframe including building, assembling, and deployment of the Java EE code from the mainframe.
For a complete listing of the Developer for z
Systems software
requirements including prerequisites and co-requisites, see the System
Requirements tab on the Developer for z
Systems product
page that
also documents the Ant specifications needed for Java EE builds in SCLM Developer Toolkit.
Attention: SCLM Developer
Toolkit uses Legacy ISPF Gateway, which implies that z/OS 1.8 or later is required. It also implies
that if Interactive ISPF Gateway is used for the TSO Commands service,
both the Legacy and the Interactive ISPF Gateway must be configured.
|
As described in PARMLIB changes, SCLM Developer Toolkit requires additional customization of system settings. These changes include the following items:
Also, SCLM Developer Toolkit uses SDSF or the TSO OUTPUT command to retrieve job completion status and job output. Both methods require additional attention:
Users require READ, WRITE, and EXECUTE permission to the z/OS UNIX directories /tmp/ and /var/zexpl/WORKAREA/
. Directory WORKAREA/ is
located in
/var/zexpl/
, unless you specified
a different location when you customized IBM Explorer
for z/OS.
SCLM Developer Toolkit uses the standard ISPF/SCLM skeletons, so ensure that the ISP.SISPSLIB skeleton library is allocated to the ISPSLIB concatenation in ISPF.conf. Using the ISP.SISPSENU data set is optional.
The following sample code shows the ISPF.conf file, which must be customized to match your system environment. Comment lines start with an asterisk (*). Add data sets to the concatenation on the same line and separate the names with a comma (,). .
* REQUIRED:
sysproc=ISP.SISPCLIB,FEK.SFEKPROC,FEL.SFELPROC
ispmlib=ISP.SISPMENU
isptlib=ISP.SISPTENU
ispplib=ISP.SISPPENU
ispslib=ISP.SISPSLIB
ispllib=ISP.SISPLOAD
* OPTIONAL:
*allocjob = ISP.SISPSAMP(ISPZISP2)
*ISPF_timeout = 900
ispslib=hlq.USERSKEL,ISP.SISPSLIB
SCLM Developer Toolkit uses some directives set in rdz.env to locate data sets and directories.
The following code sample shows the SCLMDT directives in rdz.env, which must be customized to match your system environment. For more details on customizing rdz.env, see rdz.env, the environment configuration file.
_SCLMDT_CONF_HOME=/var/rdz/sclmdt
#STEPLIB=$STEPLIB:FEL.SFELAUTH:FEL.SFELLOAD
#_SCLMDT_TRANTABLE=FEL.#CUST.LSTRANS.FILE
#ANT_HOME=/usr/lpp/Apache/Ant/apache-ant-1.7.1
_SCLMDT_BASE_HOME=$RSE_HOME
_SCLMDT_WORK_HOME=$CGI_ISPHOME
CGI_DTWORK=$_SCLMDT_WORK_HOME
SCLM Developer Toolkit provides the ability to store long name files into SCLM. Long file names are files with names that have more than 8 characters or are in mixed case. Storing of long file names is achieved through the use of a VSAM file that contains the mapping of the long file name to the 8-character member name used in SCLM.
To create the long/short name translation VSAM, customize and submit the sample FLM02LST member in the ISP.SISPSAMP ISPF sample library. The configuration steps in this publication require the VSAM to be named FEL.#CUST.LSTRANS.FILE, as shown in the following sample setup JCL.
//FLM02LST JOB <job parameters>
//*
//* CAUTION: This is neither a JCL procedure nor a complete job.
//* Before using this sample, you will have to make the following
//* modifications:
//* 1. Change the job parameters to meet your system requirements.
//* 2. Change ****** to the volume that will hold the VSAM.
//* 3. Change all references of FEL.#CUST.LSTRANS.FILE to
//* match your naming convention for the SCLM translate VSAM.
//*
//CREATE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE FEL.#CUST.LSTRANS.FILE
SET MAXCC=0
DEFINE CLUSTER(NAME(FEL.#CUST.LSTRANS.FILE) -
VOLUMES(******) -
RECORDSIZE(58 2048) -
SHAREOPTIONS(3 3) -
CYLINDERS(1 1) -
KEYS(8 0) -
INDEXED) -
DATA (NAME(FEL.#CUST.LSTRANS.FILE.DATA)) -
INDEX (NAME(FEL.#CUST.LSTRANS.FILE.INDEX))
/* DEFINE ALTERNATE INDEX WITH NONUNIQUE KEYS -> ESDS */
DEFINE ALTERNATEINDEX(-
NAME(FEL.#CUST.LSTRANS.FILE.AIX) -
RELATE(FEL.#CUST.LSTRANS.FILE) -
RECORDSIZE(58 2048) -
VOLUMES(******) -
CYLINDERS(1 1) -
KEYS(50 8) -
UPGRADE -
NONUNIQUEKEY) -
DATA (NAME(FEL.#CUST.LSTRANS.FILE.AIX.DATA)) -
INDEX (NAME(FEL.#CUST.LSTRANS.FILE.AIX.INDEX))
/*
//*
//PRIME EXEC PGM=IDCAMS,COND=(0,LT)
//SYSPRINT DD SYSOUT=*
//INITREC DD *
INITREC1
/*
//SYSIN DD *
REPRO INFILE(INITREC) -
OUTDATASET(FEL.#CUST.LSTRANS.FILE)
IF LASTCC = 4 THEN SET MAXCC=0
BLDINDEX IDS(FEL.#CUST.LSTRANS.FILE) -
ODS(FEL.#CUST.LSTRANS.FILE.AIX)
IF LASTCC = 0 THEN -
DEFINE PATH (NAME(FEL.#CUST.LSTRANS.FILE.PATH) -
PATHENTRY (FEL.#CUST.LSTRANS.FILE.AIX))
/*
Before using the long/short name translation, uncomment and set the rdz.env environment variable _SCLMDT_TRANTABLE to match the name of the long/short name translation VSAM.
This step is required only if you plan to use the Java EE build support in SCLM.
Apache Ant is an open source Java build tool and can be downloaded from http://ant.apache.org/. Ant consists of text files and scripts, which are distributed in ASCII format and thus require an ASCII/EBCDIC translation to run in z/OS UNIX.
Perform the following steps to implement Ant on z/OS, and to define it to Developer for z Systems:
JAVA_HOME=/usr/lpp/java/IBM/J6.0
ANT_HOME=/usr/lpp/Apache/Ant/apache-ant-1.7.1
To test that the Ant initialization has been successful:
Example:
export PATH=/usr/lpp/Apache/Ant/apache-ant-1.7.1/bin:$PATH
export PATH=/usr/lpp/java/J6.0/bin:$PATH
Example:
ant -version
Description |
|
Value |
---|---|---|
Developer for z Systems sample library |
|
|
Developer for z Systems sample directory |
|
|
Java bin directory |
|
|
Ant bin directory |
|
|
WORKAREA home directory |
|
|
SCLMDT project configuration home directory |
|
|
Long/short name translation VSAM |
|
SCLM Developer Toolkit and Legacy ISPF Gateway share
the same WORKAREA and /tmp directory, both of which
might need a periodic cleanup. z/OS UNIX provides a shell script, skulker,
that deletes files based on the directory they are in and their age.
Combined with the z/OS UNIX cron daemon, which runs commands
at specified dates and times, you can set up an automated tool that
periodically cleans out targeted directories. Refer to UNIX System Services Command Reference (SA22-7802)
for more information about the skulker script and the cron daemon.
The Developer for z Systems Integrated Debugger host component allows version 9.0.1 and higher clients to debug various Language Environment (LE) based applications. The Integrated Debugger requires z/OS 1.10 or higher.
See the “Integrated Debugger” section of the “Understanding Developer for z Systems” chapter in the Host Configuration Reference (SC27-8578) for an overview of the Integrated Debugger data flow.
To debug programs written in COBOL v3.4 and v4, the Integrated Debugger needs access to a listing data set (PDS or PDS/E). The data set name can be provided via environment variable AQE_DBG_V4LIST, or DD AQEV4LST. If neither is present, Integrated Debugger will form the data set name by replacing the last qualifier of the executable's data set (for example .LOAD) with .LISTING. Discuss with your developers to see which method is usable at your site.
Normally, only one Language Environment (LE) based debugger, such as the Integrated Debugger, can be active in a given application, CICS region, DB2 stored procedure, or IMS transaction. A good indication that a debugger is an LE-based debugger is that it provides a CEEEVDBG load module or alias that must be available to the application.
However, Integrated Debugger can coexist with IBM Debug Tool for z/OS, if Integrated Debugger is loaded first
by the application.
If the Developer for z Systems client uses encryption to communicate with the RSE daemon, then the (client based) Debug Engine will, by default, also use encryption to communicate with the (host based) Debug Manager. By default, the Debug Engine uses the same certificates as the Developer for z Systems client.
This implies that the RSE daemon started task and the Debug Manager started task are assumed to be set up similarly when it comes to communication encryption. The following alternate scenario’s are available for situations where encryption settings for RSE daemon and Debug Manager differ:
Unlike RSE daemon, the Debug Manager does not have native support for encrypted communication. The Debug Manager relies on a TCP/IP service called Application Transparent Transport Layer Security (AT-TLS) for encrypted communication. Refer to “Setting up AT-TLS” in the IBM Rational Developer for z Systems Host Reference Guide (SC27-8578) for a step-by-step setup guide.
Developer for z Systems is not SYSPLEX aware, and therefore requires that the program to be debugged is active on the same system the Developer for z Systems client is connected to. This includes debug sessions started via a batch job.
In z/OS 2.1, you can specify SYSAFF=* or SYSTEM=* on the JOB card to enforce that the job runs on the system it was submitted. On older systems you must explicitly specify the correct system name when using a JESPLEX to unite multiple JES subsystems in a SYSPLEX.
CEE3501S The module //IEWBNDD was not found
The Integrated Debugger requires that a Developer for z Systems supervisor call (SVC), FEL.SFELLPA(AQESVC03), is defined to your system. In ideal circumstances, this SVC is activated or updated during IPL of the system. However, IPL is not always an option, so Integrated Debugger will do a dynamic installation or update using the Debug Manager started task.
SVC defined | SVC not defined | |
---|---|---|
Version of active and new SVC match |
|
|
Version of active and new SVC do not match |
|
|
The Integrated Debugger is capable of using a Language Environment (LE) user exit that reads TEST runtime options from a data set for a given module. This is beneficial for debugging code that is active in subsystems, like IMS transactions and DB2 stored procedures, as it is not possible to provide the TEST runtime options dynamically to this code.
Define the debugger to a CICS region, as documented in the AQECSD sample CSD update job. AQECSD is located in FEL.#CUST.JCL, unless you specified a different location when you customized and submitted job FEL.SFELSAMP(FELSETUP). See Customization setup for more details.
To debug DB2 stored procedures, the Integrated Debugger requires the following DB2 related updates.
The following updates are required to use the Integrated Debugger in the remote build procedures provided by Developer for z Systems. For more information on the function and location of these JCL procedures, see Refer to ELAXF* remote build procedures.
Similar to the Developer for z Systems client, the Developer for z Systems host supports running code analysis tools, which are provided as a separate product, IBM Rational Developer for z Systems Host Utilities. A benefit of doing code analysis on the host is that it can be integrated in your daily batch processing.
Code review scans source code and reports rule violations, using rules with different severity levels. The tool comes with rule providers for Cobol and PL/I, but other rule providers can be added.
Developer for z Systems Host Utilities provides a sample procedure, AKGCR, to simplify the calling of code review services in batch mode. AKGCR is found in AKG.#CUST.PROCLIB, unless you specified a different location when you customized and submitted the AKG.SAKGSAMP(AKGSETUP) job.
Customize the sample procedure, AKG.#CUST.PROCLIB(AKGCR), as described within the member, and copy it to SYS1.PROCLIB.
//MYJOB JOB <job parameters>
//PROCS JCLLIB ORDER=(AKG.#CUST.PROCLIB)
Developer for z Systems Code Review allows for third-party code to be part of the review process. For example, you can provide a rule provider to analyze C/C++ code, or you can enhance the Cobol rule provider to recognize site-specific coding conventions.
Host-based code review is an Eclipse process, just like the Developer for z Systems client. Therefore, the enhancements done by your development support team for code review on the client can be reused on the host.
The enhancements will consist of Eclipse plugins or Eclipse features. In order to activate them, you must make them available to the existing code, as documented in the AKGCRADD configuration job. AKGCRADD is in AKG.#CUST.JCL, unless you specified a different location when you customized and submitted the AKG.SAKGSAMP(AKGSETUP) job.
Code coverage analyzes a running program and generates a report of lines that are executed, compared to the total number of executable lines. Note that Code coverage sets up a TCP/IP connection, using an ephemeral port, with IBM Debug Tool for z/OS, or with the Integrated Debugger Debug Engine of a Developer for z Systems client.
Developer for z Systems Host Utilities provides two ways to invoke Code coverage in batch mode, A sample JCL procedure, to process a single program run, and a set of scripts to start and stop a permanently active Code coverage collector that can process multiple program runs.
The AKGCC sample procedure provides a method to start a Code coverage collector, have it analyze a single program run, stop the collector and archive the results for later usage.
AKGCC is in AKG.#CUST.PROCLIB, unless you specified a different location when you customized and submitted the AKG.SAKGSAMP(AKGSETUP) job.
Customize the sample procedure, AKG.#CUST.PROCLIB(AKGCC), as described within the member, and copy it to SYS1.PROCLIB.
//MYJOB JOB <job parameters>
//PROCS JCLLIB ORDER=(AKG.#CUST.PROCLIB)
Depending on how your software development process is set up, the convenience of having the AKGCC procedure take care of everything might not outweigh the resource and time usage to start a Code coverage collector for each program analysis.
Developer for z Systems Host Utilities provides the ccstart script to start a Code coverage collector which remains active. This collector can then be used in multiple Code coverage invocations. The ccstop script can be used to stop the collector.
These scripts (ccstart, ccstop, and codecov) are located in /usr/lpp/rdzutil/bin/ if you installed Developer for z Systems Host Utilities in the default location. Usage of these scripts is documented in the Developer for z Systems IBM Knowledge Center.
The output of code coverage is intended to be imported into a Developer for z Systems client, and is therefore written to a z/OS UNIX file. Code coverage is also able to use the results of a previous run and combine them with the results of the current run, resulting in a single report that covers multiple code paths.
For these reasons, Developer for z Systems Host Utilities does not attempt to remove the output of a code coverage run, and the output will thus accumulate over time.
z/OS UNIX provides a shell script, skulker, that deletes files based on the directory they are in and their age. Combined with the z/OS UNIX cron daemon, which runs commands at specified dates and times, you can set up an automated tool that periodically cleans out targeted directories. Refer to UNIX System Services Command Reference (SA22-7802) for more information about the skulker script and the cron daemon.
This section combines various optional customization tasks. To configure the required service, follow the instructions in the appropriate section.
This customization task does not require assistance, special resources, or special customization tasks. |
Content assist for C/C++ can use the definitions in include.conf to do forced includes of specified files or members. A forced include consists of a file or directory, data set, or data set member which will be parsed when a content assist operation is performed, regardless of whether that file or member was included in the source code using a pre-processor directive.
The file must be referenced in rdz.env by the include.c or include.cpp variables before it is used. This reference in rdz.env implies that you can specify a different file for usage by C and C++. The variables in rdz.env are disabled by default.
The sample include.conf is located in /etc/zexpl/, unless you specified a different location when you customized and submitted job FEL.SFELSAMP(FELSETUP). See Customization setup for more details. You can edit the file with the TSO OEDIT command.
Definitions must start in column 1. Comment lines start with a pound sign (#) when using a US code page. Data lines can only have the name of a directory, file, data set or member. Comments are not allowed on the same line. Line continuations are not supported.
# To include the stdio.h file from the /usr/include directory, input:
# /usr/include/stdio.h
#
# To include all files of the /usr/include directory and all of it's
# sub-directories, input:
# /usr/include
#
# Uncomment and customize variable FILETYPES to limit the z/OS UNIX
# wildcard include to selected (case sensitive) file types:
# The file types are specified in a comma-delimited list (no blanks)
# FILETYPES=H,h,hpp,C,c,cpp,cxx
# To include all members of the CBC.SCLBH.H data set, input:
# //CBC.SCLBH.H
#
# To include the STDIOSTR member of the CBC.SCLBH.H data set, input:
# //CBC.SCLBH.H(STDIOSTR)
# The sample list contains some commonly used C standard library files
/usr/include/assert.h
/usr/include/ctype.h
/usr/include/errno.h
/usr/include/float.h
/usr/include/limits.h
/usr/include/locale.h
/usr/include/math.h
/usr/include/setjmp.h
/usr/include/signal.h
/usr/include/stdarg.h
/usr/include/stddef.h
/usr/include/stdio.h
/usr/include/stdlib.h
/usr/include/string.h
/usr/include/time.h
This customization task does not require assistance, special resources, or special customization tasks. |
REXEC (Remote Execution) is a TCP/IP service that enables clients to execute a command on the host system. SSH (Secure Shell) is a similar service, but all communication is encrypted. Developer for z Systems uses either service for doing remote (host-based) actions in z/OS UNIX subprojects.
REXEC and SSH rely on services provided by INETD (Internet Daemon), which is another TCP/IP service. Communications Server IP Configuration Guide (SC31-8775) describes the steps required to set up INETD, REXEC, and SSH. For more details and alternate setup methods, see the white paper Using INETD, REXEC and SSH with Developer for System z (SC14-7301), available in the Developer for z Systems library, http://www-01.ibm.com/support/docview.wss?uid=swg27038517.
exec stream tcp nowait OMVSKERN /usr/sbin/orexecd rexecd –LV
exec 512/tcp #REXEC Command Server
The same principle applies to SSH. Its common port is 22, and the server name is sshd.
This customization task does not require assistance, special resources, or special customization tasks. |
Developer for z Systems supports the interpreting and expanding COBOL and PL/I include statements, including select third-party include statements. Developer for z Systems also provides a sample REXX exec, FEKRNPLI, that can be called by the Developer for z Systems client to expand PL/I source by invoking the PL/I compiler.
FEKRNPLI is located in FEL.#CUST.CNTL, unless you specified a different location when you customized and submitted the FEL.SFELSAMP(FELSETUP) job. For more details, see Basic customization.
The Developer for z
Systems client
uses the TSO Command Service to execute the exec. This implies that
if the FEKRNPLI exec is placed in the SYSPROC or SYSEXEC concatenation
for the TSO Command Service, the user does not need to know the exact
location of the exec. The user only needs to know the name. When using
the Legacy ISPF Gateway, the SYSPROC or SYSEXEC concatenation
is defined in ISPF.conf. Customization of this file
is documented in IBM Explorer
for z/OS Host Configuration
Guide (SC27-8437).
This customization task does not require
assistance, but does require the following resources or special customization
tasks:
|
Frameworks that assist developers in writing code to perform repeatable, self-checking unit tests are collectively known as xUnit. Developer for z Systems provides such a framework for unit testing of Enterprise COBOL and PL/I code, called zUnit.
The zUnit test runner also needs access to a load library that holds the different test cases. This library is likely to be unique to a developer.
Customize the sample procedure, FEL.#CUST.PROCLIB(AZUZUNIT), as described within the member, and copy it to SYS1.PROCLIB.
The name of the procedure and the names of the steps in the procedure match the default properties that are included with the Developer for z Systems client. If the name of a procedure or the name of a step in a procedure is changed, the corresponding properties file on all of the clients must be updated. You should not change the procedure and step names.
//MYJOB JOB <job parameters>
//PROCS JCLLIB ORDER=(FEL.#CUST.PROCLIB)
rdz.env is located in /etc/zexpl/, unless you specified a different location when you customized and submitted FEL.SFELSAMP(FELSETUP) job. For more details, see Customization setup. You can edit the file with the TSO OEDIT command.
The zunit script allows the user to specify data sets that will be added to the STEPLIB directive used by the script.
The zUnit test runner allows for automatic reformatting of test reports. Developer for z Systems provides sample conversions (for example, conversion to Ant or jUnit format), which are located in /usr/lpp/ibm/rdz/samples/zunit/xsd and /usr/lpp/ibm/rdz/samples/zunit/xsl, if you installed Developer for z Systems in the default /usr/lpp/ibm/rdz location.
This customization task does not require assistance, special resources, or special customization tasks. |
You need the assistance of a CICS administrator to complete this customization
task, which requires the following resources or special customization
tasks:
|
The Developer for z Systems Enterprise Service Tools component supports different formats of Arabic and Hebrew interface messages, and bidirectional data presentation and editing in all editors and views. In terminal applications, both left-to-right and right-to-left screens are supported, and numeric fields and fields with opposite-to-screen orientation.
Additional bidirectional features and functionality include the following:
Additionally, Enterprise Service Tools-generated code can support bidi transformation in environments other than CICS SFR (Service Flow Runtime). One example is batch applications. You can make the Enterprise Service Tools generators to include calls to the bidirectional conversion routines by specifying the appropriate bidi transformation options in the Enterprise Service Tools generation wizards and linking the generated programs with the appropriate bidirectional conversion library, FEL.SFELLOAD.
CEDA DEF PROG(FEJBDCMP) LANG(LE) G(xxx)
CEDA DEF PROG(FEJBDTRX) LANG(LE) G(xxx)
This customization task does not require
assistance, but does require the following resources or special customization
tasks:
|
In all other situations, make all IRZM* and IIRZ* modules in FEL.SFELLMOD available either through STEPLIB or LINKLIST. You should do this by adding the installation data set to the concatenation so that applied maintenance is automatically available.
If you use STEPLIB, define the modules not available through LINKLIST in the STEPLIB directive of the task that executes the code.
IRZ9999S Failed to retrieve the text of a Language Environment runtime
message. Check that the Language Environment runtime message module for
facility IRZ is installed in DFHRPL or STEPLIB.
This customization task does not require assistance, but does require the following resources or special customization tasks. |
Developer for z Systems provides a sample PL/I preprocessor which can be called by the Developer for z Systems client.
Sample member FEKRNPLI is located in FEL.#CUST.CNTL,
unless you specified a different location when you customized and
submitted job FEL.SFELSAMP(FELSETUP). For more details,
see Customization setup. Customize the sample PL/I
preprocessor (REXX) exec FEL.#CUST.CNTL(FEKRNPLI),
as described within the member, and notify the Developer for z
Systems users
where the exec is located.
After completing the product customization, you can use the Installation Verification Programs (IVPs) described in this chapter to verify the successful setup of key product components.
AQECM001I Debug Manager startup complete (clientport/hostport)
If the job ends with return code 66, then FEL.SFELAUTH is not APF-authorized.
fekfivpc | CARMA connection |
fekfivps | SCLMDT connection |
A large region size is required for the user ID that executes the IVPs because functions such as Java, which require a lot of memory, are executed. You should set the region size to 131072 kilobytes (128 megabytes) or more.
CEE5213S The signal SIGPIPE was received.
%z/OS UNIX command%: command was killed by signal number 13
%line-number% *-* %REXX command%
+++ RC(137) +++
All sample commands in this section require certain environment variables to be set. This way, the IVP scripts are available through the PATH statement and the location of the customized configuration files is known. Use the pwd and cd commands to verify and change your current directory to the directory with the customized configuration files. The ivpinit shell script can then be used to set the RSE environment variables, such as in the following sample, where $ is the z/OS UNIX prompt:
$ pwd
/u/userid
$ cd /etc/zexpl
$ . ./ivpinit
-- RSE_CFG set to /etc/zexpl -- based on current location
-- RSE_HOME set to /usr/lpp/ibm/zexpl -- defined in $RSE_CFG/rse.env
-- added product $PATH to PATH
-- PATH=/etc/zexpl:/bin:/usr/lpp/java/J6.0/bin:/usr/lpp/ibm/zexpl/bin:/usr/lpp/i
spf/bin:/bin:/usr/lpp/ibm/rdz/bin:/bin
The first period (.) in . ./ivpinit is a z/OS UNIX command to run the shell in the current environment, so that the environment variables set in the shell are effective even after exiting the shell. The second period (.) is referring to the current directory.
/usr/lpp/ibm/rdz/bin/fekfivpc
Also,
if . ./ivpinit is not executed first, all fekfivp* scripts
ask for the location of the directory holding the customized configuration
filesfekfivpc
The command should return a success message.:
Verify the connection to SCLM Developer Toolkit by executing the following command:
fekfivps
The command should return a success message.
fekfivps has the following optional, non-positional, parameters:
Customize and submit the sample FELRACF job,
which has sample RACF commands
to create the basic security definitions for Developer for z
Systems.
Customize and submit the sample AQERACF job, which has sample RACF commands to create the security
definitions for Integrated Debugger.
FELRACF and AQERACF are is located in FEL.#CUST.JCL,
unless you specified a different location when you customized and
submitted the FEL.SFELSAMP(FELSETUP) job. For more details, see Customization setup.
See the RACF Command Language Reference (SA22–7687), for more information about RACF commands.
Description |
|
Value |
---|---|---|
Developer for z Systems product high-level qualifier |
|
|
Developer for z Systems customization high-level qualifier |
|
|
Integrated Debugger started task name |
|
Attention: Some products, such as FTP, require being program controlled if "WHEN PROGRAM" is active. Test this program control before activating it on a production system. |
The following sample RACF commands
create the DBGMGR started task, with protected user
ID (STCDBM) and the STCGROUP group
assigned to it.
ADDGROUP STCGROUP OMVS(AUTOGID)
DATA('GROUP WITH OMVS SEGMENT FOR STARTED TASKS')
ADDUSER STCDBM DFLTGRP(STCGROUP) NOPASSWORD NAME('DEBUG MANAGER')
OMVS(AUTOUID HOME(/tmp) PROGRAM(/bin/sh) )
DATA('Rational Developer for z Systems')
RDEFINE STARTED DBGMGR.* DATA('DEBUG MANAGER')
STDATA(USER(STCDBM) GROUP(STCGROUP) TRUSTED(NO))
Integrated Debugger requires UPDATE access to the BPX.SERVER profile to create or delete the security environment for the debug thread. Note that using UID(0) to bypass this requirement is not supported. This permit is only required when the optional Integrated Debugger feature is used.
Attention: Defining the BPX.SERVER profile
makes z/OS UNIX as a whole switch from UNIX level security to z/OS UNIX level
security, which is more secure. This switch might impact other z/OS UNIX applications
and operations. Test the security before activating it on a production
system. For more information about the different security levels,
see UNIX System Services
Planning (GA22-7800).
|
Servers with authority to BPX.SERVER must
run in a clean, program-controlled environment. This requirement implies
that all programs called by Debug Manager must also be program controlled.
For MVS load libraries, program
control is managed by your security software.
The following additional prerequisite libraries must
be made program controlled to support the use of optional services.
This list does not include data sets that are specific to a product
that Developer for z
Systems interacts with, such as IBM Explorer for z/OS.
Users require READ access to one of the listed AQE.AUTHDEBUG.* profiles to be able to use the Integrated Debugger for debugging problem-state programs. Users permitted to the AQE.AUTHDEBUG.AUTHPGM profile are also allowed to debug APF authorized programs. Replace the #apf placeholder with valid user IDs or RACF group names for those users that are allowed to debug authorized programs.
RDEFINE FACILITY AQE.AUTHDEBUG.STDPGM UACC(NONE)
PERMIT AQE.AUTHDEBUG.STDPGM CLASS(FACILITY) ACCESS(READ) ID(*)
RDEFINE FACILITY AQE.AUTHDEBUG.AUTHPGM UACC(NONE)
PERMIT AQE.AUTHDEBUG.AUTHPGM CLASS(FACILITY) ACCESS(READ) ID(#apf)
SETROPTS RACLIST(FACILITY) REFRESH
READ access for users and ALTER for system programmers is sufficient for most Developer for z Systems data sets. Replace the #sysprog placeholder with valid user IDs or RACF group names. Also, ask the system programmer who installed and configured the product for the correct data set names. FEK is the default high-level qualifier used during installation and FEL.#CUST is the default high-level qualifier for data sets created during the customization process.
ADDGROUP (FEL) OWNER(IBMUSER) SUPGROUP(SYS1)
DATA('IBM Rational Developer for z Systems - HLQ STUB')
ADDSD 'FEL.*.**' UACC(READ)
DATA('IBM Rational Developer for z Systems')
PERMIT 'FEL.*.**' CLASS(DATASET) ACCESS(ALTER) ID(#sysprog)
SETROPTS GENERIC(DATASET) REFRESH
ADDSD 'FEL.#CUST.LSTRANS.*.**' UACC(UPDATE)
DATA('IBM Rational Developer for z Systems - SCLMDT')
PERMIT 'FEL.#CUST.LSTRANS.*.**' CLASS(DATASET) ACCESS(ALTER) ID(#sysprog)
SETROPTS GENERIC(DATASET) REFRESH
ADDSD 'FEL.#CUST.CRA*.**' UACC(READ)
DATA('IBM Rational Developer for z Systems - CARMA')
PERMIT 'FEL.#CUST.CRA*.**' CLASS(DATASET) ACCESS(ALTER) ID(#sysprog)
PERMIT 'FEL.#CUST.CRA*.**' CLASS(DATASET) ACCESS(UPDATE) ID(#ram-developer)
SETROPTS GENERIC(DATASET) REFRESH
Use the following sample commands to display the results of your security-related customizations.
If you are a previous user of Developer for z Systems, save the related customized files before installing this version of IBM Developer for z Systems.
Assign an application environment for a DB2 stored procedure.
In version 9.5.1, the RSE and JES Job Monitor
related functions moved fromIBM
Rational Developer for z Systems to another product, IBM Explorer
for z/OS. IBM Explorer for z/OS is
now a prerequisite for IBM
Rational Developer for z Systems.
IBM strongly advises you
to redo all customizations using the new z/OS Explorer and Developer for z
Systems
samples to ensure you are using the new MVS data set names and z/OS UNIX paths.
SMP/E data sets:
MVS data sets:
z/OS UNIX paths:
this updates the default location where the LE user exit is stored, so users might need to update their LE user exit usage
users might need to update their procedure invocation to use the new Developer for z Systems path, /usr/lpp/ibm/rdz/samples/zunit/*
Configurable files
Table 17 shows an overview of Developer for z Systems files that are customized in version 9.5.1. The Developer for z Systems sample libraries, FEL.SFELSAMP, FEL.SFELSAMV and /usr/lpp/ibm/rdz/samples/, contain more customizable members than listed here, such as sample CARMA source code and jobs to compile them.
Note: Sample job FELSETUP copies all listed members to different data sets and directories, default FEL.#CUST.* and /etc/zexpl/*.
Member/File | Default location | Purpose | Migration notes |
---|---|---|---|
FELSETUP |
|
JCL to create data sets and directories, and populate them with customizable files | New, configuration is required |
DBGMGR |
|
JCL for Debug Manager | Using new data set/path names |
AQEJCL |
|
Name for DBGMGR member | See DBGMBR member |
ELAXF* |
|
JCL for remote project builds, and so on | Using new data set/path names |
FELRACF |
|
JCL for security definitions | New, configuration is required |
AQERACF |
|
JCL for Debug Manager | Using new data set/path names |
CRA$VMSG |
|
JCL to create the CARMA message VSAM | Using new data set/path names |
CRA$VDEF |
|
JCL to create the CARMA configuration VSAM | Using new data set/path names |
CRA$VSTR |
|
JCL to create the CARMA custom information VSAM | Using new data set/path names |
CRA$VCAD |
|
JCL to create the CARMA configuration VSAM for CA Endevor® SCM RAM | Using new data set/path names |
CRA$VCAS |
|
JCL to create the CARMA custom information VSAM for CA Endevor® SCM RAM | Using new data set/path names |
CRASUBMT |
|
CARMA batch startup CLIST | Using new data set/path names |
CRASUBCA |
|
CARMA batch startup CLIST for CA Endevor® SCM RAM | Using new data set/path names |
CRACFG |
|
CARMA interaction configuration for CA Endevor® SCM RAM | None |
CRABCFG |
|
CARMA batch actions configuration for CA Endevor® SCM RAM | None |
CRABATCA |
|
CARMA batch action JCL for CA Endevor® SCM RAM | None |
CRASCL |
|
Template SCL for CA Endevor® SCM | None |
CRASHOW |
|
CARMA configuration for CA Endevor® SCM RAM | None |
CRATMAP |
|
CARMA configuration for CA Endevor® SCM RAM | None |
CRANDVRA |
|
CARMA allocation REXX for CA Endevor® SCM RAM | None |
CRADYNDA |
|
CARMA allocation REXX for CA Endevor® SCM RAM | None |
CRAALLOC |
|
CARMA allocation REXX | None |
CRA#VSLM |
|
JCL to create the SCLM RAM's message VSAM | Using new data set/path names |
CRA#ASLM |
|
JCL to create the SCLM RAM's data sets | Using new data set/path names |
CRA#VPDS |
|
JCL to create the PDS RAM's message VSAM | Using new data set/path names |
CRA#UADD |
|
JCL to merge RAM definitions | Using new data set/path names |
CRA#UQRY |
|
JCL to extract RAM definitions | Using new data set/path names |
CRAXJCL |
|
Sample source code for IRXJCL replacement | None |
CRA#CIRX |
|
JCL to compile CRAXJCL | Using new data set/path names |
AQECSD |
|
JCL to define Integrated Debugger to CICS regions | None |
AQED3CEE |
|
JCL to create customized LE runtime modules | Using new data set/path names |
AQED3CXT |
|
JCL to create LE user exit | Using new data set/path names |
FEKTEP2 |
|
SQL command input used by ELAXF* | None |
FEKTIAD |
|
SQL command input used by ELAXF* | None |
AZUZUNIT |
|
JCL procedure for zUnit | Using new data set/path names |
FEKRNPLI |
|
REXX to call the PL/I compiler from within the preprocessor framework | None |
IRZCSD |
|
JCL to define Enterprise Service Tools to CICS | None |
rdz.env |
|
RSE environment variables | Older copies must be replaced by this one and the customizations done again. |
CRASRV.properties |
|
CARMA configuration file | None |
crastart.conf |
|
CARMA configuration file for CRASTART usage | Using new data set/path names |
crastart.endevor.conf |
|
CARMA configuration file for CRASTART usage for CA Endevor® SCM RAM | Using new data set/path names |
include.conf |
|
Forced includes for C/C++ content assist | None |
Table 18 shows an overview of customizable files that moved to z/OS Explorer in version 9.5.1.
Note: Sample job FEKSETUP copies all listed members to different data sets and directories, default FEK.#CUST.* and /etc/zexpl/*.
Member/File | Default location | Purpose | Migration notes |
---|---|---|---|
FEKSETUP |
|
JCL to create data sets and directories, and populate them with customizable files | Updated to remove actions for files that are no longer used and add actions for new files |
JMON |
|
JCL for JES Job Monitor | None |
FEJJJCL |
|
Name for JMON member | See JMON member |
RSED |
|
JCL for RSE daemon | None |
FEKRSED |
|
Name for RSED member | See RSED member |
FEKRACF |
|
JCL for security definitions | Removed Developer for z Systems specific data |
FEJJCNFG |
|
JES Job Monitor configuration file | None |
FEJTSO |
|
JCL for TSO submits | None |
FEKLOGS |
|
JCL to collect log files | Using new data set/path names Removed Developer for z Systems specific data |
rse.env |
|
RSE environment variables | Older copies of rsed.envvars must be replaced by this one and the customizations done again. |
ISPF.conf |
|
ISPF Gateway configuration file | Using new data set/path names |
ssl.properties |
|
RSE encrypted communication configuration file | None |
rsecomm.properties |
|
RSE trace configuration file | None |
pushtoclient.properties |
|
Push information to the client configuration file | Using new data set/path names |
Table 19 shows an overview of files that are customized in version 9.5.1. The Developer for z Systems Host Utilities sample libraries, AKG.SAKGSAMP and /usr/lpp/rdzutil/samples, contain more customizable members than listed here, such as sample code review post-processing script.
Member or File | Default location | Purpose | Migration notes |
---|---|---|---|
AKGSETUP |
|
JCL to create data sets, and populate them with customizable files | None |
AKGCC |
|
JCL for code coverage | None |
AKGCR |
|
JCL for code review | None |
AKGCRADD |
|
JCL to add third-party code to code review | None |
These notes are for a migration from a base version 9.1 to version 9.5. It includes changes that are already documented as part of version 9.1 maintenance. The changes that are part of the maintenance stream, and thus possibly already implemented, are marked with the release where they were introduced.
It is advised to replace an existing rsed.envvars (by default in /etc/rdz) with the newly provided sample (by default in /usr/lpp/rdz/samples) and redo the customizations.
Table 20 shows an overview of files that are customized in version 9.5. The Developer for z Systems sample libraries, FEK.SFEKSAMP, FEK.SFEKSAMV and /usr/lpp/rdz/samples/, contain more customizable members than listed here, such as sample CARMA source code and jobs to compile them.
Member/File | Default location | Purpose | Migration notes |
---|---|---|---|
FEKSETUP |
|
JCL to create data sets and directories, and populate them with customizable files | Updated to remove actions for files that are no longer used and add actions for new files |
JMON |
|
JCL for JES Job Monitor | None |
FEJJJCL |
|
Name for JMON member | See JMON member |
RSED |
|
JCL for RSE daemon | None |
FEKRSED |
|
Name for RSED member | See RSED member |
DBGMGR |
|
JCL for Debug Manager | SFEKLPA added to STEPLIB |
AQEJCL |
|
Name for DBGMGR member | See DBGMBR member |
ELAXF* |
|
JCL for remote project builds, and so on | SFEKAUTH added to STEPLIB |
FEKRACF |
|
JCL for security definitions | New AQE.** profiles |
AQERACF |
|
JCL for Debug Manager | New AQE.** profiles |
FEKPBITS |
|
JCL to alter access permits for log files | None |
FEJJCNFG |
|
JES Job Monitor configuration file | None |
FEJTSO |
|
JCL for TSO submits | None |
CRA$VMSG |
|
JCL to create the CARMA message VSAM | None |
CRA$VDEF |
|
JCL to create the CARMA configuration VSAM | None |
CRA$VSTR |
|
JCL to create the CARMA custom information VSAM | None |
CRA$VCAD |
|
JCL to create the CARMA configuration VSAM for CA Endevor® SCM RAM | VSAM input has changed |
CRA$VCAS |
|
JCL to create the CARMA custom information VSAM for CA Endevor® SCM RAM | VSAM input has changed |
CRASUBMT |
|
CARMA batch startup CLIST | None |
CRASUBCA |
|
CARMA batch startup CLIST for CA Endevor® SCM RAM | Added DD APIHJC and new DD’s |
CRACFG |
|
CARMA interaction configuration for CA Endevor® SCM RAM | Optional directives added |
CRABCFG |
|
CARMA batch actions configuration for CA Endevor® SCM RAM | Optional directives added |
CRABATCA |
|
CARMA batch action JCL for CA Endevor® SCM RAM | None |
CRASCL |
|
Template SCL for CA Endevor® SCM | New, configuration is optional |
CRASHOW |
|
CARMA configuration for CA Endevor® SCM RAM | None |
CRATMAP |
|
CARMA configuration for CA Endevor® SCM RAM | None |
CRANDVRA |
|
CARMA allocation REXX for CA Endevor® SCM RAM | Allocate new DD |
CRADYNDA |
|
CARMA allocation REXX for CA Endevor® SCM RAM | New, configuration is optional |
CRAALLOC |
|
CARMA allocation REXX | None |
CRA#VSLM |
|
JCL to create the SCLM RAM's message VSAM | None |
CRA#ASLM |
|
JCL to create the SCLM RAM's data sets | None |
CRA#VPDS |
|
JCL to create the PDS RAM's message VSAM | None |
CRA#UADD |
|
JCL to merge RAM definitions | None |
CRA#UQRY |
|
JCL to extract RAM definitions | None |
CRAXJCL |
|
Sample source code for IRXJCL replacement | None |
CRA#CIRX |
|
JCL to compile CRAXJCL | None |
AQECSD |
|
JCL to define Integrated Debugger to CICS regions | Define new resources |
AQED3CEE |
|
JCL to create customized LE runtime modules | Updated to ensure correct LE exit is used |
AQED3CXT |
|
JCL to create LE user exit | New debug level for LE exit |
FEKTEP2 |
|
SQL command input used by ELAXF* | None |
FEKTIAD |
|
SQL command input used by ELAXF* | None |
AZUZUNIT |
|
JCL procedure for zUnit | SFEKAUTH added to STEPLIB |
FEKRNPLI |
|
REXX to call the PL/I compiler from within the preprocessor framework | None |
IRZCSD |
|
JCL to define Enterprise Service Tools to CICS | New, configuration is optional |
FEKLOGS |
|
JCL to collect log files | None |
rsed.envvars |
|
RSE environment variables | Older copies must be replaced by this one and the customizations done again. |
ISPF.conf |
|
TSO/ISPF Client Gateway configuration file | None |
CRASRV.properties |
|
CARMA configuration file | None |
crastart.conf |
|
CARMA configuration file for CRASTART usage | None |
crastart.endevor.conf |
|
CARMA configuration file for CRASTART usage for CA Endevor® SCM RAM | Added DD APIHJC and new DD’s |
include.conf |
|
Forced includes for C/C++ content assist | None |
ssl.properties |
|
RSE encrypted communication configuration file | None |
rsecomm.properties |
|
RSE trace configuration file | None |
pushtoclient.properties |
|
Push information to the client configuration file | None |
Table 21 shows an overview of files that are customized in version 9.5. The Developer for z Systems Host Utilities sample libraries, AKG.SAKGSAMP and /usr/lpp/rdzutil/samples, contain more customizable members than listed here, such as sample code review post-processing script.
Member or File | Default location | Purpose | Migration notes |
---|---|---|---|
AKGSETUP |
|
JCL to create data sets, and populate them with customizable files | None |
AKGCC |
|
JCL for code coverage | None |
AKGCR |
|
JCL for code review | New DDs SYSLIB, LIST, and JUNIT |
AKGCRADD |
|
JCL to add third-party code to code review | None |
The following migration notes are specific to IBM Rational Developer for z Systems version 9.1. These notes are valid for migration fromIBM Rational Developer for z Systemsversion 9.1.0 to version 9.1.1, and they are additions to the existing version 9.1.0 migration notes.
All of the listed changes are valid since version 9.1.1.
These notes are for a migration from a base version 9.0 to version 9.1. It includes changes that are already documented as part of version 9.0 maintenance. The changes that are part of the maintenance stream, and thus possibly already implemented, are marked with the release where they were introduced.
It is advised to replace an existing rsed.envvars (by default in /etc/rdz) with the newly provided sample (by default in /usr/lpp/rdz/samples) and redo the customizations.
Table 22 shows an overview of files that are customized in version 9.1.0. The Developer for z Systems sample libraries, FEK.SFEKSAMP, FEK.SFEKSAMV and /usr/lpp/rdz/samples/, contain more customizable members than listed here, such as sample CARMA source code and jobs to compile them.
Member/File | Default location | Purpose | Migration notes |
---|---|---|---|
FEKSETUP |
|
JCL to create data sets and directories, and populate them with customizable files | Updated to remove actions for files that are no longer used and add actions for new files |
JMON |
|
JCL for JES Job Monitor | None |
FEJJJCL |
|
Name for JMON member | See JMON member |
RSED |
|
JCL for RSE daemon | None |
FEKRSED |
|
Name for RSED member | See RSED member |
DBGMGR |
|
JCL for Debug Manager | New, customization is optional |
AQEJCL |
|
Name for DBGMGR member | See DBGMBR member |
ELAXF* |
|
JCL for remote project builds, and so on | ELAXFGO includes SFEKAUTH in STEPLIB |
FEKRACF |
|
JCL for security definitions | New, started task DBGMGR |
AQERACF |
|
JCL for Debug Manager | New, customization is optional |
FEKPBITS |
|
JCL to alter access permits for log files | New, customization is optional |
FEJJCNFG |
|
JES Job Monitor configuration file | None |
FEJTSO |
|
JCL for TSO submits | None |
CRA$VMSG |
|
JCL to create the CARMA message VSAM | None |
CRA$VDEF |
|
JCL to create the CARMA configuration VSAM | None |
CRA$VSTR |
|
JCL to create the CARMA custom information VSAM | None |
CRA$VCAD |
|
JCL to create the CARMA configuration VSAM for CA Endevor® SCM RAM | VSAM input has changed |
CRA$VCAS |
|
JCL to create the CARMA custom information VSAM for CA Endevor® SCM RAM | VSAM input has changed |
CRASUBMT |
|
CARMA batch startup CLIST | Added support for 8 startup arguments, DD CRAPARM and allocation exec |
CRASUBCA |
|
CARMA batch startup CLIST for CA Endevor® SCM RAM | Added support for 8 startup arguments, DD CRAPARM and new DD’s |
CRACFG |
|
CARMA interaction configuration for CA Endevor® SCM RAM | New, configuration is optional |
CRABCFG |
|
CARMA batch actions configuration for CA Endevor® SCM RAM | None |
CRABATCA |
|
CARMA batch action JCL for CA Endevor® SCM RAM | None |
CRASHOW |
|
CARMA configuration for CA Endevor® SCM RAM | None |
CRATMAP |
|
CARMA configuration for CA Endevor® SCM RAM | None |
CRANDVRA |
|
CARMA allocation REXX for CA Endevor® SCM RAM | Added support for user exit and allocate new DD |
CRAALLOC |
|
CARMA allocation REXX | New, configuration is optional |
CRA#VSLM |
|
JCL to create the SCLM RAM's message VSAM | None |
CRA#ASLM |
|
JCL to create the SCLM RAM's data sets | None |
CRA#VPDS |
|
JCL to create the PDS RAM's message VSAM | None |
CRA#UADD |
|
JCL to merge RAM definitions | None |
CRA#UQRY |
|
JCL to extract RAM definitions | None |
CRAXJCL |
|
Sample source code for IRXJCL replacement | None |
CRA#CIRX |
|
JCL to compile CRAXJCL | None |
AQECSD |
|
JCL to define Integrated Debugger to CICS regions | New, configuration is optional |
AQED3CEE |
|
JCL to create customized LE runtime modules | New, configuration is optional |
AQED3CXT |
|
JCL to create LE user exit | New, configuration is optional |
ADNCSDRS |
|
JCL to define the RESTful CRD server to primary CICS region | None |
ADNCSDTX |
|
JCL to define alternate transaction IDs to CICS region | None |
ADNTXNC |
|
JCL to create alternate transaction IDs | None |
ADNMSGHC |
|
JCL to compile ADNMSGHS | None |
ADNMSGHS |
|
Sample source code for the Pipeline Message Handler | None |
ADNVCRD |
|
JCL to create the CRD repository | None |
ADNCSDWS |
|
JCL to define the Web Service CRD server to primary CICS region | None |
ADNCSDAR |
|
JCL to define the CRD server to non-primary CICS regions | None |
ADNJSPAU |
|
JCL to update the CRD defaults | None |
ADNVMFST |
|
JCL to create and define the Manifest repository | None |
FEKTEP2 |
|
SQL command input used by ELAXF* | None |
FEKTIAD |
|
SQL command input used by ELAXF* | None |
AZUZUNIT |
|
JCL procedure for zUnit | None |
FEKRNPLI |
|
REXX to call the PL/I compiler from within the preprocessor framework | None |
FEKLOGS |
|
JCL to collect log files | None |
rsed.envvars |
|
RSE environment variables | Older copies must be replaced by this one and the customizations done again. |
ISPF.conf |
|
TSO/ISPF Client Gateway configuration file | None |
CRASRV.properties |
|
CARMA configuration file | Added support for user exit |
crastart.conf |
|
CARMA configuration file for CRASTART usage | Added support for 8 startup arguments, DD CRAPARM and allocation exec |
crastart.endevor.conf |
|
CARMA configuration file for CRASTART usage for CA Endevor® SCM RAM | Added support for 8 startup arguments, DD CRAPARM and new DD’s |
include.conf |
|
Forced includes for C/C++ content assist | None |
ssl.properties |
|
RSE encrypted communication configuration file | None |
rsecomm.properties |
|
RSE trace configuration file | Added support for USER keyword |
pushtoclient.properties |
|
Push information to the client configuration file | None |
Table 23 shows an overview of files that are customized in version 9.1. The Developer for z Systems Host Utilities sample libraries, AKG.SAKGSAMP and /usr/lpp/rdzutil/samples, contain more customizable members than listed here, such as sample code review post-processing script.
Member or File | Default location | Purpose | Migration notes |
---|---|---|---|
AKGSETUP |
|
JCL to create data sets, and populate them with customizable files | None |
AKGCC |
|
JCL for code coverage | None |
AKGCR |
|
JCL for code review | New DDs BIMPORT and BEXPORT |
AKGCRADD |
|
JCL to add third-party code to code review | None |
These notes are for a migration from a base version 8.5 to version 9.0. It includes changes that are already documented as part of version 8.5 maintenance. The changes that are part of the maintenance stream, and thus possibly already implemented, are marked with the release where they were introduced.
Table 24 shows an overview of files that are customized in version 9.0. The Developer for z Systems sample libraries, FEK.SFEKSAMP, FEK.SFEKSAMV and /usr/lpp/rdz/samples/, contain more customizable members than listed here, such as sample CARMA source code and jobs to compile them.
Member/File | Default location | Purpose | Migration notes |
---|---|---|---|
FEKSETUP |
|
JCL to create data sets and directories, and populate them with customizable files | Updated to remove actions for files that are no longer used and add actions for new files |
JMON |
|
JCL for JES Job Monitor | None |
FEJJJCL |
|
Name for JMON member | See JMON member |
RSED |
|
JCL for RSE daemon | None |
FEKRSED |
|
Name for RSED member | See RSED member |
ELAXF* |
|
JCL for remote project builds, and so on | ELAXFSP and ELAXFSQL are new, ELAXFCOC and ELAXFCP1 are updated for Cobol Version 5 support |
FEKRACF |
|
JCL for security definitions | None |
FEJJCNFG |
|
JES Job Monitor configuration file | New optional directives have been added. Existing optional directives have been removed. |
FEJTSO |
|
JCL for TSO submits | None |
CRA$VMSG |
|
JCL to create the CARMA message VSAM | None |
CRA$VDEF |
|
JCL to create the CARMA configuration VSAM | Added support to exclude RAMs |
CRA$VSTR |
|
JCL to create the CARMA custom information VSAM | None |
CRA$VCAD |
|
JCL to create the CARMA configuration VSAM for CA Endevor® SCM RAM | Added support to exclude RAMs and VSAM input has changed. |
CRA$VCAS |
|
JCL to create the CARMA custom information VSAM for CA Endevor® SCM RAM | VSAM input has changed |
CRASUBMT |
|
CARMA batch startup CLIST | None |
CRASUBCA |
|
CARMA batch startup CLIST for CA Endevor® SCM RAM | None |
CRABCFG |
|
CARMA batch actions configuration for CA Endevor® SCM RAM | New directives added |
CRABATCA |
|
CARMA batch action JCL for CA Endevor® SCM RAM | Added support for variable JOB card |
CRASHOW |
|
CARMA configuration for CA Endevor® SCM RAM | None |
CRATMAP |
|
CARMA configuration for CA Endevor® SCM RAM | None |
CRANDVRA | FEK.SFEKPROC | CARMA allocation REXX for CA Endevor® SCM RAM | Added new DD allocations |
CRA#VSLM |
|
JCL to create the SCLM RAM's message VSAM | None |
CRA#ASLM |
|
JCL to create the SCLM RAM's data sets | None |
CRA#VPDS |
|
JCL to create the PDS RAM's message VSAM | None |
CRA#UADD |
|
JCL to merge RAM definitions | None |
CRA#UQRY |
|
JCL to extract RAM definitions | None |
CRAXJCL |
|
Sample source code for IRXJCL replacement | None |
CRA#CIRX |
|
JCL to compile CRAXJCL | None |
ADNCSDRS |
|
JCL to define the RESTful CRD server to primary CICS region | None |
ADNCSDTX |
|
JCL to define alternate transaction IDs to CICS region | None |
ADNTXNC |
|
JCL to create alternate transaction IDs | None |
ADNMSGHC |
|
JCL to compile ADNMSGHS | None |
ADNMSGHS |
|
Sample source code for the Pipeline Message Handler | None |
ADNVCRD |
|
JCL to create the CRD repository | None |
ADNCSDWS |
|
JCL to define the Web Service CRD server to primary CICS region | None |
ADNCSDAR |
|
JCL to define the CRD server to non-primary CICS regions | None |
ADNJSPAU |
|
JCL to update the CRD defaults | None |
ADNVMFST |
|
JCL to create and define the Manifest repository | None |
FEKTEP2 |
|
SQL command input used by ELAXF* | New, customization is optional |
FEKTIAD |
|
SQL command input used by ELAXF* | New, customization is optional |
AZUZUNIT |
|
JCL procedure for zUnit | None |
FEKRNPLI |
|
REXX to call the PL/I compiler from within the preprocessor framework | None |
FEKLOGS |
|
JCL to collect log files | Added additional checks. Any customization to older files must be done again. |
rsed.envvars |
|
RSE environment variables | Older copies must be replaced by this one and the customizations done again. |
ISPF.conf |
|
TSO/ISPF Client Gateway configuration file | None |
CRASRV.properties |
|
CARMA configuration file | Added support for default values |
crastart.conf |
|
CARMA configuration file for CRASTART usage | None |
crastart.endevor.conf |
|
CARMA configuration file for CRASTART usage for CA Endevor® SCM RAM | None |
include.conf |
|
Forced includes for C/C++ content assist | None |
ssl.properties |
|
RSE encrypted communication configuration file | None |
rsecomm.properties |
|
RSE trace configuration file | None |
pushtoclient.properties |
|
Push information to the client configuration file | None |
There are no migration notes, because there is no equivalent function in version 8.5.
Table 25 shows an overview of files that are customized in version 9.0. The Developer for z Systems Host Utilities sample libraries, AKG.SAKGSAMP and /usr/lpp/rdzutil/samples, contain more customizable members than listed here, such as sample code review post-processing script.
Member or File | Default location | Purpose | Migration notes |
---|---|---|---|
AKGSETUP |
|
JCL to create data sets, and populate them with customizable files | None |
AKGCC |
|
JCL for code coverage | None |
AKGCR |
|
JCL for code review | New DDs BIMPORT and BEXPORT |
AKGCRADD |
|
JCL to add third-party code to code review | None |
This section summarizes the information in IBM Rational Developer for z Systems Host Configuration Reference (SC27-8578). For more details, see that publication.
The Developer for z Systems host system consists of several components that interact to give the client access to the host system services and data. Understanding the design of these components can help you make the correct configuration decisions.
Developer for z
Systems
interacts with other host components, which has security implications.
Developer for z Systems uses TCP/IP to provide mainframe access to users on a non-mainframe workstation. It also uses TCP/IP for communication between various components and other products.
Unlike traditional z/OS applications, Developer for z Systems is not a monolithic application that can be identified easily to Workload Manager (WLM). Developer for z Systems consists of several components that interact to give the client access to the host system services and data. Some of these services are active in different address spaces, resulting in different WLM classifications.
Developer for z
Systems extends
the z/OS Explorer push-to-client,
or host-based client control, with support for project definitions.
This chapter contains information useful for a CICS Transaction Server administrator.
This section is provided to assist you with some common problems that you may encounter when setting up Application Transparent Transport Layer Security (AT-TLS), or during checking or modifying an existing setup.
The following publications are referenced in this document:
Publication title | Order number | Reference | Reference Web site |
---|---|---|---|
Program Directory for IBM Rational Developer for z Systems | GI11-8298 | Developer for z Systems | http://www-01.ibm.com/support/docview.wss?uid=swg27038517 |
Program Directory for IBM Rational Developer for z Systems Host Utilities | GI13-2864 | Developer for z Systems | http://www-01.ibm.com/support/docview.wss?uid=swg27038517 |
IBM Rational Developer for z Systems Host Configuration Guide | SC27-8577 | Developer for z Systems | http://www-01.ibm.com/support/docview.wss?uid=swg27038517 |
IBM Rational Developer for z Systems Host Configuration Reference | SC27-8578 | Developer for z Systems | http://www-01.ibm.com/support/docview.wss?uid=swg27038517 |
IBM Rational Developer for z Systems Common Access Repository Manager Developer's Guide | SC23-7660 | Developer for z Systems | http://www-01.ibm.com/support/docview.wss?uid=swg27038517 |
SCLM Developer Toolkit Administrator's Guide | SC23-9801 | Developer for z Systems | http://www-01.ibm.com/support/docview.wss?uid=swg27038517 |
IBM Explorer for z/OS Host Configuration Guide | SC27-8437 | z/OS Explorer | |
IBM Explorer for z/OS Host Configuration Reference | SC27-8438 | z/OS Explorer | |
Communications Server IP CICS Sockets Guide | SC31-8807 | z/OS 1.13 | http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/ |
Communications Server IP Configuration Guide | SC31-8775 | z/OS 1.13 | http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/ |
Communications Server IP Configuration Reference | SC31-8776 | z/OS 1.13 | http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/ |
MVS Initialization and Tuning Guide | SA22-7591 | z/OS 1.13 | http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/ |
MVS Initialization and Tuning Reference | SA22-7592 | z/OS 1.13 | http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/ |
MVS JCL Reference | SA22-7597 | z/OS 1.13 | http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/ |
MVS Planning Workload Management | SA22-7602 | z/OS 1.13 | http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/ |
MVS System Commands | SA22-7627 | z/OS 1.13 | http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/ |
Security Server RACF Command Language Reference | SA22-7687 | z/OS 1.13 | http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/ |
Security Server RACF Security Administrator's Guide | SA22-7683 | z/OS 1.13 | http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/ |
UNIX System Services Command Reference | SA22-7802 | z/OS 1.13 | http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/ |
UNIX System Services Planning | GA22-7800 | z/OS 1.13 | http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/ |
UNIX System Services User's Guide | SA22-7801 | z/OS 1.13 | http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/ |
Using REXX and z/OS UNIX System Services | SA22-7806 | z/OS 1.13 | http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/ |
Description | Reference Web site |
---|---|
Developer for z Systems IBM Knowledge Center | http://www-01.ibm.com/support/knowledgecenter/SSQ2R2/rdz_welcome.html |
Developer for z Systems Library | http://www-01.ibm.com/support/docview.wss?uid=swg27038517 |
Developer for z Systems home page | http://www-03.ibm.com/software/products/en/developerforsystemz/ |
Developer for z Systems Recommended service | http://www-01.ibm.com/support/docview.wss?rs=2294&context=SS2QJ2&uid=swg27006335 |
Developer for z Systems enhancement request | https://www.ibm.com/developerworks/support/rational/rfe/ |
Download Apache Ant | http://ant.apache.org/ |
Publication title | Order number | Reference | Reference website |
---|---|---|---|
ABCs of z/OS System Programming Volume 9 (z/OS UNIX) | SG24-6989 | Redbook | http://www.redbooks.ibm.com/ |
System Programmer’s Guide to: Workload Manager | SG24-6472 | Redbook | http://www.redbooks.ibm.com/ |
TCPIP Implementation Volume 1: Base Functions, Connectivity, and Routing | SG24-7532 | Redbook | http://www.redbooks.ibm.com/ |
TCPIP Implementation Volume 3: High Availability, Scalability, and Performance | SG24-7534 | Redbook | http://www.redbooks.ibm.com/ |
TCP/IP Implementation Volume 4: Security and Policy-Based Networking | SG24-7535 | Redbook | http://www.redbooks.ibm.com/ |
Tivoli® Directory Server for z/OS | SG24-7849 | Redbook | http://www.redbooks.ibm.com/ |
This information was developed for products and services offered in the US. This material might be available from IBM in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.
IBM may use or distribute any of the information you provide in any way it believes appropriate without incurring any obligation to you.
IBM Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
The performance data and client examples cited are presented for illustrative purposes only. Actual performance results may vary depending on specific configurations and operating conditions.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to actual people or business enterprises is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Permissions for the use of these publications are granted subject to the following terms and conditions.
These terms and conditions are in addition to any terms of use for the IBM website.
You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM.
You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM.
Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein.
IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed.
You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations.
IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.shtml.
Adobe and PostScript are trademarks of Adobe Systems Incorporated.
Cell Broadband Engine - Sony Computer Entertainment Inc.
Rational is a trademark of International Business Machines Corporation and Rational Software Corporation, in the United States, other countries, or both.
Intel, Intel Centrino, Intel SpeedStep, Intel Xeon, Celeron, Itanium, and Pentium are trademarks of Intel Corporation in the United States, or other countries, or both.
IT Infrastructure Library is a trademark of Central Computer and Telecommunications Agency
ITIL is a trademark of The Minister for the Cabinet Office
Linear Tape-Open, LTO, and Ultrium are trademarks of HP, IBM Corp., and Quantum
Linux is a trademark of Linus Torvalds
Microsoft, Windows, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation in the United States, or other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.