Note: Before using this information, be sure to read the
general information under Notices.
|
This edition applies to IBM® Rational® Developer for System z® Version 9.1.1 (program number 5724-T07) and to all subsequent releases and modifications until otherwise indicated in new editions.
Order publications by phone or fax. IBM Software Manufacturing Solutions takes publication orders between 8:30 a.m. and 7:00 p.m. eastern standard time (EST). The phone number is (800) 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, 2014
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 System z functions. It includes brief instructions on how to configure IBM Rational Developer for System z Version 9.1.1 on the z/OS® host system. For complete details on the configuration of this product, see IBM Rational Developer for System z Host Configuration Guide (SC23-7658).
The information in this document applies to all of the IBM Rational Developer for System z Version 9.1.1 packages.
For the most up-to-date versions of this document, see the IBM Rational Developer for System z Host Configuration Quickstart Guide (GI11-9201) available at http://www-05.ibm.com/e-business/linkweb/publications/servlet/pbi.wss?CTY=US&FNC=SRX&PBL=GI11-9201.
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 System z 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 System z Version 9.1.1.
It lists and briefly documents the different steps that are needed to do a basic setup of the products. For more details on the listed actions and non-default settings, see IBM Rational Developer for System z Host Configuration Guide (SC23-7658).
To use this book, you must be familiar with the z/OS UNIX System Services and MVS™ host systems.
Developer for System z 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 System z. These requisites must be installed and operational at runtime for the corresponding feature to work as designed.
The IBM Rational Developer for System z Prerequisites Guide (SC23-7659) has a list of prerequisite software that must be installed and operational before Developer for System z will work. There is also a list of corequisite software to support specific features of Developer for System z. These requisites must be installed and operational at runtime for the corresponding feature to work as designed. The most up-to-date version of this publication can be found on the library page of the Developer for System z website (http://www-01.ibm.com/software/sw-library/en_US/products/Z964267S85716U24/).
A basic setup for Developer for System z requires the allocation of the systems resources listed in Table 1.
Resource | Default value |
---|---|
![]() ![]() |
![]() ![]() |
APF-authorized data set | FEK.SFEKAUTH |
started task | JMON, and RSED |
port for host-confined communication | 6715 |
port for client-host communication | 4035 |
port range for client-host communication | any available port is used |
z/OS UNIX server security definition | UPDATE permission to BPX.SERVER for RSED started task |
PassTicket security definitions | no default |
MVS build procedures | ELAXF* |
Table 2 lists the administrators who are needed for basic customization tasks.
Administrator | Task |
---|---|
System | Typical system programmer actions are required for all of the customization tasks |
Security |
|
TCP/IP | Define new TCP/IP ports |
WLM | Assign started task goals to the servers and their child processes |
The user ID of a Developer for System z user must have the following attributes:
Developer for System z consists of the following permanently active servers, which can be started tasks or user jobs. These servers provide the requested services themselves, or start other servers such as z/OS UNIX threads or user jobs, to provide the service:
Developer for System z is designed to support the installing of products once, followed by the copying of a minimal set of necessary data sets and directories to other systems for deployment. Running multiple copies, whether same or different version, of the products on the same system is also supported.
During an upgrade, before installing the product, make backups of all of the configuration files because the installation process might overwrite the files.
This chapter summarizes the basic customization information in IBM Rational Developer for System z Host Configuration Guide (SC23-7658). For more details, see that publication.
Developer for System z comes with several sample configuration files and sample JCL. To avoid overwriting your customizations when applying maintenance, you should copy all these members and z/OS UNIX files to a different location and to customize the copy.
Some functions of Developer for System z also 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, FEKSETUP, is provided to create the copies and the required directories.
Customize and submit sample member FEKSETUP in data set FEK.SFEKSAMP to create customizable copies of configuration files and configuration JCL, and to create required z/OS UNIX directories. The required customization steps are described within the member.
Note that the listed PARMLIB changes are for a basic setup only. More changes are needed if you select to use certain optional functions.
MAXASSIZE specifies the maximum address space (process) region size. Set MAXASSIZE in SYS1.PARMLIB(BPXPRMxx) to 2G, which is the maximum value allowed.
MAXTHREADS specifies the maximum number of active threads for a single process. Set MAXTHREADS in SYS1.PARMLIB(BPXPRMxx) to 1500 or higher.
MAXTHREADTASKS specifies the maximum number of active MVS tasks for a single process. Set MAXTHREADTASKS in SYS1.PARMLIB(BPXPRMxx) to 1500 or higher.
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.
These values can be checked and set dynamically until the next IPL with the following console commands:
To start the Developer for System z RSE and JMON servers automatically at next system IPL, add the start commands to SYS1.PARMLIB(COMMANDxx).
After the servers are defined and configured, they can be started dynamically with the following console commands:
To start the Developer for System z requires that the modules in the FEK.SFEKLPA load library are in the Link Pack Area (LPA) for RSE daemon to work with data sets.
LPA data sets are defined in SYS1.PARMLIB(LPALSTxx).
For JES Job Monitor to access JES spool files, the modules in the FEK.SFEKAUTH load library and the CEE.SCEERUN* Language Environment® (LE) runtime libraries must be APF-authorized.
For ISPF to create the TSO/ISPF Client Gateway, the ISP* modules in SYS1.LINKLIB must be APF-authorized.
By default, APF authorizations are defined in SYS1.PARMLIB(PROGxx).
Set the APF authorizations dynamically until the next IPL with the following console commands, where volser is the volume on which the data set resides if it is not SMS managed:
The RSE server is a z/OS UNIX process that requires access to MVS load libraries. The following (prerequisite) libraries must be made available, either through STEPLIB or LINKLIST/LPALIB:
LINKLIST data sets are defined in SYS1.PARMLIB(PROGxx), if your site followed IBM recommendations. LPA data sets are defined in SYS1.PARMLIB(LPALSTxx).
The started task and remote build procedures listed below must reside in a system procedure library defined to your JES subsystem. In the instructions below, the IBM default procedure library, SYS1.PROCLIB, is used.
Customize the sample started task member FEK.#CUST.PROCLIB(JMON), as described within the member, and copy it to SYS1.PROCLIB. As shown in the code sample below, you have to provide the following:
//*
//* JES JOB MONITOR
//*
//JMON PROC PRM=, * PRM='-TV' TO START TRACING
// LEPRM='RPTOPTS(ON)',
// HLQ=FEK,
// CFG=FEK.#CUST.PARMLIB(FEJJCNFG)
//*
//JMON EXEC PGM=FEJJMON,REGION=0M,TIME=NOLIMIT,
// PARM=('&LEPRM,ENVAR("_CEE_ENVFILE_S=DD:ENVIRON")/&PRM')
//STEPLIB DD DISP=SHR,DSN=&HLQ..SFEKAUTH
//ENVIRON DD DISP=SHR,DSN=&CFG
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
// PEND
//*
Customize the sample started task member FEK.#CUST.PROCLIB(RSED), as described within the member, and copy it to SYS1.PROCLIB. As shown in the code sample below, you have to provide the following:
//*
//* RSE DAEMON
//*
//RSED PROC IVP=, * 'IVP' to do an IVP test
// PORT=,
// CNFG='/etc/rdz',
// HOME='/usr/lpp/rdz'
//*
//RSED EXEC PGM=BPXBATSL,REGION=0M,TIME=NOLIMIT,
// PARM='PGM &HOME./bin/rsed.sh &IVP -C&CNFG -P&PORT'
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
// PEND
//*
Developer for System z 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, and 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 3.
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 doing COBOL Compiles, Integrated CICS translate and integrated DB2® translate |
ELAXFCOP | Sample procedure for doing DB2 preprocess of EXEC SQL statements embedded in COBOL programs |
ELAXFCOT | Sample procedure for doing CICS translation for EXEC CICS statements embedded in COBOL programs |
ELAXFCPC | Sample procedure for doing C compiles |
ELAXFCPP | Sample procedure for doing C++ compiles |
ELAXFCP1 | Sample procedure for COBOL compiles 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 doing DB2 preprocess 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 doing PL/I compiles, integrated CICS translate, and integrated DB2 translate |
ELAXFPP1 | Sample procedure for PL/I compiles 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 generated DB2 code in TSO mode |
ELAXFUOP | Sample procedure for generating the UOPT step when building programs that run in CICS or IMS subsystems |
Customize the FEK.#CUST.PROCLIB(ELAXF*) sample build procedure members, 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 4.
Product | Default HLQ | Value |
---|---|---|
Rational Developer for System z | FEK | |
CICS | CICSTS42.CICS | |
DB2 | DSNA10 | |
IMS | IMS | |
COBOL | IGY.V4R2M0 | |
PL/I | IBMZ.V4R2M0 | |
C/C++ | CBC | |
LE | CEE | |
system LINKLIB | SYS1 | |
system MACLIB | SYS1 |
Product | Default DSN | Value |
---|---|---|
Developer for System z– SQL samples | FEK.#CUST.SQL | |
DB2 run library | DSNA10.RUNLIB.LOAD |
If the ELAXF* procedures cannot be copied into a system procedure library, ask the Developer for System z users to add a JCLLIB card immediately after the JOB card to the job properties on the client.
//MYJOB JOB <job parameters>
//PROCS JCLLIB ORDER=(FEK.#CUST.PROCLIB)
To create the security definitions for Developer for System z, customize and submit the FEKRACF sample member in the FEK.#CUST.JCL data set. The user submitting this job must have security administrator privileges, such as being RACF® SPECIAL. For more details, see Security definitions.
JES Job Monitor (JMON) provides all JES-related services. The behavior of JES Job Monitor can be controlled with the definitions in FEJJCNFG.
FEJJCNFG is located in FEK.#CUST.PARMLIB, unless a different location was specified when the FEK.SFEKSAMP(FEKSETUP) job was customized and submitted. For more details, see Customization setup.
Customize the FEJJCNFG sample JES Job Monitor configuration member, as shown in the following code sample:
SERV_PORT=6715
TZ=EST5EDT
#APPLID=FEKAPPL
#AUTHMETHOD=SAF
#CODEPAGE=UTF-8
#CONCHAR=$
#CONSOLE_NAME=JMON
#GEN_CONSOLE_NAME=OFF
#HOST_CODEPAGE=IBM-1047
#LIMIT_COMMANDS=NOLIMIT
#LIMIT_CONSOLE=LIMITED
#LIMIT_VIEW=USERID
#LISTEN_QUEUE_LENGTH=5
#LOOPBACK_ONLY=ON
#MAX_DATASETS=32
#MAX_THREADS=200
#TIMEOUT=3600
#TIMEOUT_INTERVAL=1200
#TRACE_STORAGE=OFF
#SEARCHALL=OFF
#SUBMIT_TIMEOUT=30
#SUBMITMETHOD=TSO
#TSO_TEMPLATE=FEK.#CUST.CNTL(FEJTSO)
The RSE server processes (RSE daemon, RSE thread pool, and RSE server) use the definitions in rsed.envvars. Optional Developer for System z and third-party services can use this configuration file also to define environment variables for their use.
rsed.envvars is located in /etc/rdz/, unless you specified a different location when you customized and submitted job FEK.SFEKSAMP(FEKSETUP). See Customization setup for more details. You can edit the file with the TSO OEDIT command.
#=============================================================
# (1) required definitions
JAVA_HOME=/usr/lpp/java/J6.0
RSE_HOME=/usr/lpp/rdz
_RSE_RSED_PORT=4035
_RSE_JMON_PORT=6715
RSE_HLQ=FEK
_RSE_HOST_CODEPAGE=IBM-1047
TZ=EST5EDT
LANG=C
PATH=/bin:/usr/sbin
_CEE_DMPTARG=/tmp
STEPLIB=NONE
_RSE_JAVAOPTS=""
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Xms128m -Xmx512m"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Ddaemon.log=/var/rdz/logs"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Duser.log=/var/rdz/logs"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDSTORE_LOG_DIRECTORY="
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dlog.retention.period=5"
#=============================================================
# (2) required definitions for TSO/ISPF Client Gateway
CGI_ISPHOME=/usr/lpp/ispf
CGI_ISPCONF=/etc/rdz
CGI_ISPWORK=/var/rdz
_RSE_ISPF_OPTS=""
#=============================================================
# (3) required definitions for SCLM Developer Toolkit
#=============================================================
# (4) optional definitions
#_RSE_PORTRANGE=8108-8118
#=============================================================
# (5) do not change unless directed by IBM support center
_RSE_SAF_CLASS=/usr/include/java_classes/IRRRacf.jar
_CEE_RUNOPTS="ALL31(ON) HEAP(32M,32K,ANYWHERE,KEEP,,) TRAP(ON)"
_BPX_SHAREAS=YES
_BPX_SPAWN_SCRIPT=YES
_EDC_ADD_ERRNO2=1
JAVA_PROPAGATE=NO
RSE_DSN_SFEKLOAD=$RSE_HLQ.SFEKLOAD
RSE_LIB=$RSE_HOME/lib
PATH=.:$JAVA_HOME/bin:$RSE_HOME/bin:$CGI_ISPHOME/bin:$PATH
LIBPATH=$JAVA_HOME/bin:$JAVA_HOME/bin/classic:$RSE_LIB:$RSE_LIB/icuc
LIBPATH=.:/usr/lib:$LIBPATH
CLASSPATH=$RSE_LIB:$RSE_LIB/dstore_core.jar:$RSE_LIB/clientserver.jar
CLASSPATH=$CLASSPATH:$RSE_LIB/dstore_extra_server.jar
CLASSPATH=$CLASSPATH:$RSE_LIB/zosserver.jar
CLASSPATH=$CLASSPATH:$RSE_LIB/dstore_miners.jar
CLASSPATH=$CLASSPATH:$RSE_LIB/universalminers.jar:$RSE_LIB/mvsminers.jar
CLASSPATH=$CLASSPATH:$RSE_LIB/carma.jar:$RSE_LIB/luceneminer.jar
CLASSPATH=$CLASSPATH:$RSE_LIB/mvsluceneminer.jar:$RSE_LIB/cdzminer.jar
CLASSPATH=$CLASSPATH:$RSE_LIB/mvscdzminer.jar:$RSE_LIB/jesminers.jar
CLASSPATH=$CLASSPATH:$RSE_LIB/debug_miner.jar
LASSPATH=$CLASSPATH:$RSE_LIB/mvsutil.jar:$RSE_LIB/jesutils.jar
CLASSPATH=$CLASSPATH:$RSE_LIB/lucene-core-2.3.2.jar
CLASSPATH=$CLASSPATH:$RSE_LIB/cdtparser.jar:$RSE_LIB/wdzBidi.jar
CLASSPATH=$CLASSPATH:$_RSE_SAF_CLASS
CLASSPATH=.:$CLASSPATH
_RSE_PTC=$_RSE_LDAP_PTC_GROUP_SUFFIX
_RSE_ISPF_OPTS="&SESSION=SPAWN$_RSE_ISPF_OPTS"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dldap.server.address=$_RSE_LDAP_SERVER"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dldap.server.port=$_RSE_LDAP_PORT"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dldap.ptc.group.name.suffix=$_RSE_PTC"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DISPF_OPTS='$_RSE_ISPF_OPTS'"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DA_PLUGIN_PATH=$RSE_LIB"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Xbootclasspath/p:$RSE_LIB/bidiTools.jar"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dfile.encoding=$_RSE_HOST_CODEPAGE"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dconsole.encoding=$_RSE_HOST_CODEPAGE"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDSTORE_INITIAL_SIZE=0"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDSTORE_MAX_FREE=0"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDSTORE_SPIRIT_ON=true"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DSPIRIT_EXPIRY_TIME=90"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DSPIRIT_INTERVAL_TIME=6"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dcom.ibm.cacheLocalHost=true"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Duser.home=$HOME"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dclient.username=$RSE_USER_ID"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dlow.heap.usage.ratio=15"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dmaximum.heap.usage.ratio=40"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDSTORE_KEEPALIVE_ENABLED=true"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDSTORE_KEEPALIVE_RESPONSE_TIMEOUT=60000"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDSTORE_IO_SOCKET_READ_TIMEOUT=180000"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DRSECOMM_LOGFILE_MAX=0"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Djob.monitor.port=$_RSE_JMON_PORT"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dlock.info.timeout=10000"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -showversion"
_RSE_SERVER_CLASS=org.eclipse.dstore.core.server.Server
_RSE_DAEMON_CLASS=com.ibm.etools.zos.server.RseDaemon
_RSE_POOL_SERVER_CLASS=com.ibm.etools.zos.server.ThreadPoolProcess
_RSE_SERVER_TIMEOUT=120000
_SCLMDT_BASE_HOME=$RSE_HOME
_SCLMDT_WORK_HOME=$_CMDSERV_WORK_HOME
CGI_DTWORK=$_SCLMDT_WORK_HOME
_CMDSERV_BASE_HOME=$CGI_ISPHOME
_CMDSERV_CONF_HOME=$CGI_ISPCONF
_CMDSERV_WORK_HOME=$CGI_ISPWORK
#=============================================================
# (6) additional environment variables
STEPLIB=$STEPLIB:CEE.SCEERUN:CEE.SCEERUN2:CBC.SCLBDLL
STEPLIB=$STEPLIB:ISP.SISPLOAD:ISP.SISPLPA:SYS1.LINKLIB
ISPF's TSO/ISPF Client Gateway uses the definitions in ISPF.conf to create a valid environment to execute batch TSO and ISPF commands. Developer for System z uses this environment to run some MVS based services.
ISPF.conf is located in /etc/rdz/, unless you specified a different location when you customized and submitted job FEK.SFEKSAMP(FEKSETUP). See Customization setup for more details. You can edit the file with the TSO OEDIT command.
Comment lines start with an asterisk (*). When concatenating data set names, add them on the same line and separate the names with a comma (,).
Besides providing the correct names for the ISPF data sets, you must also add the TSO Commands service data set name, FEK.SFEKPROC, to the SYSPROC or SYSEXEC statement, as shown in the following code sample.
* REQUIRED:
sysproc=ISP.SISPCLIB,FEK.SFEKPROC
ispmlib=ISP.SISPMENU
isptlib=ISP.SISPTENU
ispplib=ISP.SISPPENU
ispslib=ISP.SISPSLIB
ispllib=ISP.SISPLOAD
* OPTIONAL:
*allocjob = ISP.SISPSAMP(ISPZISP2)
*ISPF_timeout = 900
This chapter summarizes the installation verification information in IBM Rational Developer for System z Host Configuration Guide (SC23-7658). For more details, see that publication.
FEJ211I Server ready to accept connections.
If the job ends with return code 66, FEK.SFEKAUTH is not APF authorized.
Start the RSED started task or user job with the IVP=IVP parameter. With this parameter, the server ends after doing some installation verification tests. The output of these tests is available in DD STDOUT. In case of certain errors, data also is available in DD STDERR.
FEK002I RseDaemon started. (port=4035)
MODIFY RSED,APPL=IVP PASSTICKET,userid
MODIFY RSED,APPL=IVP DAEMON,userid
MODIFY RSED,APPL=IVP ISPF,userid
Customize and submit the FEKRACF sample member in the FEK.#CUST.JCL data set, which has sample RACF and z/OS UNIX commands to create the basic security definitions for Developer for System z.
Description |
|
Value |
---|---|---|
Developer for System z product high-level qualifier |
|
|
Developer for System z customization high-level qualifier |
|
|
JES Job Monitor started task name |
|
|
RSE daemon started task name |
|
SETROPTS LIST
SETROPTS GENERIC(FACILITY)
SETROPTS CLASSACT(FACILITY) RACLIST(FACILITY)
SETROPTS GENERIC(STARTED)
RDEFINE STARTED ** STDATA(USER(=MEMBER) GROUP(STCGROUP) TRACE(YES))
SETROPTS CLASSACT(STARTED) RACLIST(STARTED)
SETROPTS GENERIC(CONSOLE)
SETROPTS CLASSACT(CONSOLE) RACLIST(CONSOLE)
SETROPTS GENERIC(OPERCMDS)
SETROPTS CLASSACT(OPERCMDS) RACLIST(OPERCMDS)
SETROPTS GENERIC(APPL)
SETROPTS CLASSACT(APPL) RACLIST(APPL)
SETROPTS GENERIC(PTKTDATA)
SETROPTS CLASSACT(PTKTDATA) RACLIST(PTKTDATA)
RDEFINE PROGRAM ** ADDMEM('SYS1.CMDLIB'//NOPADCHK) UACC(READ)
SETROPTS WHEN(PROGRAM)
Attention: Some products, such as FTP, require to be program controlled if "WHEN PROGRAM" is active. Test this before activating it on a production system. |
ALTUSER #userid
OMVS(UID(#user-identifier) HOME(/u/#userid) PROGRAM(/bin/sh) NOASSIZEMAX)
ALTGROUP #group-name OMVS(GID(#group-identifier))
ADDGROUP STCGROUP OMVS(AUTOGID)
DATA('GROUP WITH OMVS SEGMENT FOR STARTED TASKS')
ADDUSER STCJMON DFLTGRP(STCGROUP) NOPASSWORD NAME('RDZ - JES JOBMONITOR')
OMVS(AUTOUID HOME(/tmp) PROGRAM(/bin/sh)
DATA('RATIONAL DEVELOPER FOR SYSTEM Z')
ADDUSER STCRSE DFLTGRP(STCGROUP) NOPASSWORD NAME('RDZ - RSE DAEMON')
OMVS(AUTOUID HOME(/tmp) PROGRAM(/bin/sh) ASSIZEMAX(2147483647)
DATA('RATIONAL DEVELOPER FOR SYSTEM Z')
RDEFINE STARTED JMON.* DATA('RDZ - JES JOBMONITOR')
STDATA(USER(STCJMON) GROUP(STCGROUP) TRUSTED(NO))
RDEFINE STARTED RSED.* DATA('RDZ - RSE DAEMON')
STDATA(USER(STCRSE) GROUP(STCGROUP) TRUSTED(NO))
SETROPTS RACLIST(STARTED) REFRESH
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 the profile on
a production system.
|
Servers with authority to BPX.SERVER must run in a clean, program-controlled environment. This requirement implies that all programs called by the RSE server must also be program controlled. For MVS load libraries, program control is managed by your security software.
Attention: The client connection
request fails if PassTickets are not set up correctly.
|
RDEFINE APPL FEKAPPL UACC(READ)
DATA('RATIONAL DEVELOPER FOR SYSTEM Z')
SETROPTS RACLIST(APPL) REFRESH
JES Job Monitor issues all JES operator commands requested by a user through an extended MCS (EMCS) console, whose name is controlled with the CONSOLE_NAME directive, as documented in FEJJCNFG, JES Job Monitor configuration file.
RDEFINE OPERCMDS MVS.MCSOPER.#console UACC(READ)
DATA('RATIONAL DEVELOPER FOR SYSTEM Z')
RDEFINE OPERCMDS JES%.** UACC(NONE)
PERMIT JES%.** CLASS(OPERCMDS) ACCESS(UPDATE) WHEN(CONSOLE(JMON)) ID(*)
SETROPTS RACLIST(OPERCMDS) REFRESH
READ access for users and ALTER for system programmers is sufficient for most Developer for System z data sets.
ADDGROUP (FEK) OWNER(IBMUSER) SUPGROUP(SYS1)
DATA('RATIONAL DEVELOPER FOR SYSTEM Z - HLQ STUB')
ADDSD 'FEK.*.**' UACC(READ)
DATA('RATIONAL DEVELOPER FOR SYSTEM Z')
PERMIT 'FEK.*.**' CLASS(DATASET) ACCESS(ALTER) ID(#sysprog)
SETROPTS GENERIC(DATASET) REFRESH
Use the following sample commands to display the results of your security-related customizations.
This section summarizes the migration information in IBM Rational Developer for System z Host Configuration Guide (SC23-7658). For more details, see that publication.
The following migration notes are specific to IBM Rational Developer for System z version
9.1. These notes are valid for migration fromIBM Rational Developer for System zversion
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.
This chapter provides an overview of the available operator (or console) commands for Developer for System z. If you are unfamiliar with the syntax diagrams used to explain the command format, see How to read a syntax diagram.
The MODIFY command can be used to dynamically query and change the characteristics of an active task. The abbreviated version of the command is the letter F.
>>>STORAGE TRACE (console request)<<<
LDAREGRQ 00000000000 00000000K 00000M requested region size
below 16M line
LDASIZA 00006266880 00006120K 00005M maximum region size
LDALIMIT 00006266880 00006120K 00005M limit
LDAVVRG 00006266880 00006120K 00005M getmain limit
LDALOAL 00000061440 00000060K 00000M in use
LDAHIAL 00000266240 00000260K 00000M LSQA/SWA/private subpools
_GAP 00000000000 00000000K 00000M gaps in allocation
_AVAIL 00005939200 00005800K 00005M available (including gaps)
_MAX 00006000640 00005860K 00005M current limit
above 16M line
LDAESIZA 01905262592 01860608K 01817M maximum region size
LDAELIM 01905262592 01860608K 01817M limit
LDAEVVRG 01905262592 01860608K 01817M getmain limit
LDAELOAL 00000937984 00000916K 00000M in use
LDAEHIAL 00012754944 00012456K 00012M ELSQA/ESWA/private subpools
_EGAP 00000000000 00000000K 00000M gaps in allocation
_EAVAIL 01891569664 01847236K 01803M available (including gaps)
_EMAX 01892507648 01848152K 01804M current limit
S0 userid USER 4:04(elapsed) 4:04(idle)
Users: 1
N or NONE | Startup messages only |
E or ERROR | Startup and Error messages only (default) |
I or INFO | Startup, Error, and Informational messages |
V or VERBOSE | Startup, Error, Informational, and Verbose messages |
Detailed tracing will cause performance degradations and should only be done under the direction of the IBM support center.
N or NONE | No messages. |
E or ERROR | Error messages only |
W or WARNING | Error and Warning messages |
I or INFO | Error, Warning, and Informational messages (default) |
V or VERBOSE | Error Warning, Informational, and Verbose messages |
Detailed tracing will cause performance degradations and should only be done under the direction of the IBM support center.
ProcessId(<processid>) ASId(<asid>) JobName(<jobname>)
Clients(<local>/<total>) Order(<startup order>)
<clientid><userid><connected since>
LOGON TIME------------------ ID----- USERID--
<connected since> <clientid> <userid>
ID----- USERID-- LOGON TIME------------------
<clientid> <userid> <connected since>
USERID-- ID----- LOGON TIME------------------
<userid> <clientid> <connected since>
FEK217I <dataset[(member)]> is locked by <userid>
FEK218I <dataset[(member)]> is not locked
FEK219E Failed to determine lock owner for <dataset[(member)]>
ProcessId(<processid>) Memory Usage(<java heap usage>%)
Clients(<number of clients>) Order(<startup order>) <error status>
Status | Description |
---|---|
*severe error* | The thread pool process encountered an unrecoverable error and halted operations. The other status fields show the last known values. To remove this entry from the table, use the CLEANUP option of the DISPLAY PROCESS modify command. |
*killed process* | The thread pool process was killed by Java, z/OS UNIX or an operator command. The other status fields show the last known values. To remove this entry from the table, use the CLEANUP option of the DISPLAY PROCESS modify command. |
*timeout* | The thread pool process did not respond in a timely manner to RSE daemon during a client connect request. The other status fields show the current values. The thread pool is excluded for future client connect requests. The *timeout* status is reset when a client served by this thread pool logs off. |
*rejectLogon* | The thread pool temporarily will not accept logon requests due to a heavy workload. Note that the logon request will be honored by another thread pool. Once the resource intensive task - for example, uploading a large file to a client - has completed, the *rejectLogon* status is reset. |
More information is provided when the DETAIL option of the DISPLAY PROCESS modify command is used:
ProcessId(33555087) ASId(002E) JobName(RSED8) Order(1)
PROCESS LIMITS: CURRENT HIGHWATER LIMIT
JAVA HEAP USAGE(%) 10 56 100
CLIENTS 0 25 30
MAXFILEPROC 83 103 64000
MAXPROCUSER 97 99 200
MAXTHREADS 9 14 1500
MAXTHREADTASKS 9 14 1500
The ASId field is the address space ID, in hexadecimal notation. The process limits table shows the current resource usage, the high-water mark for the resource usage, and the resource limit. Due to other limiting factors, the defined limit might never be reached.
ProcessId(421 ) ASId(007D) JobName(RSED8) Order(1)
USERID THREAD-ID TCB@ ACC_TIME TAG
STCRSE 0EDE540000000000 005E6B60 822 1/ThreadPoolProcess
STCRSE 0EDE870000000001 005E69C8 001
STCRSE 0EDE980000000002 005E6518 1814
STCRSE 0EDEBA0000000003 005E66B0 2305
STCRSE 0EDECB0000000004 005E62F8 001
STCRSE 0EDEDC0000000005 005E60D8 001
STCRSE 0EDF860000000006 005C2BF8 628 6/ThreadPoolMonitor$Memory
UsageMonitor
STCRSE 0EDF970000000007 005C2D90 003 7/ThreadPoolMonitor
STCRSE 0EDFDB0000000008 005C29D8 001
STCRSE 0EE22E000000000E 005C1BE0 070
IBMUSER 0EE0EB0000000011 005C22B8 276 20/ServerReceiver
IBMUSER 0EE2500000000012 005C19C0 137 16/ServerUpdateHandler
IBMUSER 0EE2610000000013 005C17A0 509 15/ServerCommandHandler
IBMUSER 0EE1840000000014 005C1E00 065 21/ZosSystemMiner
STCRSE 0EE1510000000016 005C2098 078
STCRSE 0EE1950000000017 005C1580 001
IBMUSER 0EE23F0000000018 005C1360 021 26/UniversalFileSystemMine
r
IBMUSER 0EE2A5000000001C 005C0CF0 003 27/EnvironmentMiner
IBMUSER 0EE283000000001D 005C1140 002 31/CommandMiner
IBMUSER 0EE272000000001E 005C0E88 081 32/MVSFileSystemMiner
IBMUSER 0EE294000000001F 005C0AD0 002 33/MVSByteStreamHandler$Op
enCloseThread
STCRSE 0EE2E90000000023 005C0470 001
IBMUSER 0EE2C70000000024 005C08B0 050 38/JESMiner
IBMUSER 0EE2B60000000026 005C0690 004 40/FAMiner
IBMUSER 0EE30B0000000027 005C0250 002 41/LuceneMiner
IBMUSER 0EE31C0000000028 005C0030 002 42/CDTParserMiner
IBMUSER 0EE32D0000000029 005BDE00 002 43/MVSLuceneMiner
IBMUSER 0EE33E000000002A 005BDBE0 002 44/CDTMVSParserMiner
ProcessId(421 ) ASId(007D) JobName(RSED8) Order(1) CONTINUATION
USERID THREAD-ID TCB@ ACC_TIME TAG
The output is limited to the first 4000 threads for each thread pool.
When a client connection is cancelled, the host system threads go through normal termination processing to clean up resources used by them. This action implies that some threads can take a few minutes before they end; for example, because they are waiting on the keep-alive mechanism to time out.
When a client connection is cancelled, the host system threads go through normal termination processing to clean up resources used by them. This action implies that some threads can take a few minutes before they end; for example, because they are waiting on the keep-alive mechanism to time out.
FEK220I Host logs are written onto /tmp/feklogs.CDFMVS08.RSED.log
By default, only the server logs are collected. Command options allow you to collect different logs:USER | Collect log files for the specified user ID’s |
AUDIT | Collect audit logs |
NOSERVER | Do not collect server logs |
Developer for System z will query your security product for access permits to FEK.CMD.LOGS.** profiles to determine if the requestor is allowed to collect the specified logs. By default, the requestor is the RSED started task user ID, unless the OWNER option is specified. Only the requestor has access to the file holding the collected data.
E or 0 or OFF | Error messages only. |
W or 1 | Error and warning messages. This is the default setting in rsecomm.properties. |
I or 2 or ON | Error, warning, and informational messages. |
Detailed tracing will cause performance degradations and should only be done under the direction of the IBM support center.
E or 0 or OFF | Error messages only. |
W or 1 | Error and warning messages. This is the default setting in rsecomm.properties. |
I or 2 or ON | Error, warning, and informational messages. |
Detailed tracing will cause performance degradations and should only be done under the direction of the IBM support center.
E or 0 or OFF | Error messages only. |
W or 1 | Error and warning messages. This is the default setting in rsecomm.properties. |
I or 2 or ON | Error, warning, and informational messages. |
Detailed tracing will cause performance degradations and should only be done under the direction of the IBM support center.
Detailed tracing will cause performance degradations and should only be done under the direction of the IBM support center.
OFF | Error messages only |
ON (default) | Error, warning, and informational messages. |
FFS | Set the specified log level only for MVS data set services (lock.log and ffs*.log) |
RSECOMM | Set the specified log level only for RSE server (rsecomm.log) |
The command can be issued for users that are currently not logged on. The setting remains active when a user logs off and will be used again when the user logs on.
Use the USER directive in rsecomm.properties to simulate issuing the MODIFY TRACE USER command at server startup. Existing settings from previous MODIFY TRACE USER or MODIFY TRACE SERVER operator commands or the USER directive in rsecomm.properties will be replaced by the setting of this command.
Detailed tracing will cause performance degradations and should only be done under the direction of the IBM support center.
OFF | Error messages only. |
ON (default) | Error, warning, and informational messages. |
The command alters the trace detail level for RSE server (rsecomm.log) and the MVS data set services (lock.log and ffs*.log). The command can be issued for users that are currently not logged on. The setting remains active when a user logs off and will be used again when the user logs on. Use the USER directive in rsecomm.properties to simulate issuing the MODIFY TRACE USER command at server startup. Existing settings from previous MODIFY TRACE USER or MODIFY TRACE SERVER operator commands or the USER directive in rsecomm.properties will be replaced by the setting of this command.
Detailed tracing will cause performance degradations and should only be done under the direction of the IBM support center.
OFF | Error messages only. |
ON (default) | Error, warning, and informational messages. |
The command alters the trace detail level for RSE server (rsecomm.log) and the MVS data set services (lock.log and ffs*.log). Existing settings from previous MODIFY TRACE USER or MODIFY TRACE SERVER operator commands or the USER directive in rsecomm.properties will be replaced by the setting of this command.
Detailed tracing will cause performance degradations and should only be done under the direction of the IBM support center.
JVMDUMP034I User requested Heap dump using '/tmp/heapdump.20120223.211'
430.16777590.0001.phd' through JVMRI
JVMDUMP034I User requested Java dump using '/tmp/javacore.20120223.214
244.16777590.0002.phd' through JVMRI
+FEK900I DAEMON IVP: SSL is disabled
+FEK900I DAEMON IVP: connected
+FEK900I DAEMON IVP: 1977
+FEK900I DAEMON IVP: 6902918
+FEK900I DAEMON IVP: Success
+FEK901I DAEMON IVP Exit code = 0
+FEK900I ISPF IVP: executed on CDFMVS08 -- Tue Sep 13 22:29:28 EDT 2011
+FEK900I ISPF IVP: executed by uid=1(IBMUSER) gid=0(SYS1)
+FEK900I ISPF IVP: using /etc/rdz/rsed.envvars
+FEK900I ISPF IVP: current address space size limit is 2147483647
(2048.0 MB)
+FEK900I ISPF IVP: maximum address space size limit is 2147483647
(2048.0 MB)
+FEK900I ISPF IVP: -----------------------------------------------------
--------
+FEK900I ISPF IVP: /etc/rdz/ISPF.conf content:
+FEK900I ISPF IVP: -----------------------------------------------------
--------
+FEK900I ISPF IVP: ispllib=ISP.SISPLOAD
+FEK900I ISPF IVP: ispmlib=ISP.SISPMENU
+FEK900I ISPF IVP: isptlib=ISP.SISPTENU
+FEK900I ISPF IVP: ispplib=ISP.SISPPENU
+FEK900I ISPF IVP: ispslib=ISP.SISPSLIB
+FEK900I ISPF IVP: sysproc=ISP.SISPCLIB,FEK.SFEKPROC
+FEK900I ISPF IVP: -----------------------------------------------------
--------
+FEK900I ISPF IVP: Host install verification for RSE
+FEK900I ISPF IVP: Review IVP log messages from HOST below :
+FEK900I ISPF IVP: -----------------------------------------------------
--------
+FEK900I ISPF IVP: Service level 22Feb2011
+FEK900I ISPF IVP: RSE connection and base TSO/ISPF session initializati
on check only
+FEK900I ISPF IVP: *** CHECK : ENVIRONMENT VARIABLES - key variables
displayed below :
+FEK900I ISPF IVP: Server PATH = .:/usr/lpp/java/J6.0/bin:/usr/l
pp/rdz/bin:/usr/lpp/ispf/bin:/bin:/usr/sbin
+FEK900I ISPF IVP: STEPLIB = NONE
+FEK900I ISPF IVP: Temporary directory = /tmp
+FEK900I ISPF IVP: CGI_ISPHOME = /usr/lpp/ispf
+FEK900I ISPF IVP: CGI_ISPCONF = /etc/rdz
+FEK900I ISPF IVP: CGI_ISPWORK = /var/rdz
+FEK900I ISPF IVP: -----------------------------------------------------
--------
+FEK900I ISPF IVP: *** CHECK : USS MODULES
+FEK900I ISPF IVP: Checking ISPF Directory : /usr/lpp/ispf
+FEK900I ISPF IVP: Checking modules in /usr/lpp/ispf/bin directory
+FEK900I ISPF IVP: Checking for ISPF configuration file ISPF.conf
+FEK900I ISPF IVP: RC=0
+FEK900I ISPF IVP: MSG: SUCCESSFUL
+FEK900I ISPF IVP: -----------------------------------------------------
--------
+FEK900I ISPF IVP: *** CHECK : TSO/ISPF INITIALIZATION
+FEK900I ISPF IVP: ( TSO/ISPF session will be initialized )
+FEK900I ISPF IVP: RC=0
+FEK900I ISPF IVP: MSG: SUCCESSFUL
+FEK900I ISPF IVP: -----------------------------------------------------
--------
+FEK900I ISPF IVP: *** CHECK: Shutting down TSO/ISPF IVP session
+FEK900I ISPF IVP: RC=0
+FEK900I ISPF IVP: MSG: SUCCESSFUL
+FEK900I ISPF IVP: -----------------------------------------------------
--------
+FEK900I ISPF IVP: Host installation verification completed successfully
+FEK900I ISPF IVP: -----------------------------------------------------
--------
+FEK901I ISPF IVP Exit code = 0
+FEK900I PASSTICKET IVP: the default applid=FEKAPPL
+FEK900I PASSTICKET IVP: Success, PassTicket IVP finished normally
+FEK901I PASSTICKET IVP Exit code = 0
The syntax diagram shows you how to specify a command so that the operating system can correctly interpret what you type. Read the syntax diagram from left to right and from top to bottom, following the horizontal line, which is the main path.
The following symbols are used in syntax diagrams:
Symbol | Description |
---|---|
>> | Marks the beginning of the syntax diagram. |
> | Indicates that the syntax diagram is continued. |
| | Marks the beginning and end of a fragment or part of the syntax diagram. |
>< | Marks the end of the syntax diagram. |
The following types of operands are used in syntax diagrams:
>>──REQUIRED_OPERAND──><
>>─┬──────────────────┬─><
└─OPTIONAL_OPERAND─┘
┌─DEFAULT_OPERAND─┐
>>─┴─────────────────┴─><
Operands are classified as keywords or variables:
In the following example, the USER command is a keyword. The required variable parameter is user_id, and the optional variable parameter is password. Replace the variable parameters with your own values:
>>──USER──user_id─┬──────────┬──────────────────────────────────><
└─password─┘
If a diagram shows a character that is not alphanumeric, such as parentheses, periods, commas, equal signs, and blank spaces, you must code the character as part of the syntax. In this example, you must code OPERAND=(001 0.001):
>>──OPERAND──=──(──001── ──0.001──)────────────────────────><
An arrow returning to the left in a group of operands means that more than one can be selected, or that a single one can be repeated:
>>──┬──────────────────────┬────────────────────────────><
├─REPEATABLE_OPERAND_1─┤
├─REPEATABLE_OPERAND_2─┤
└─<────────────────────┘
If a diagram is longer than one line, the first line ends with a single arrowhead and the second line begins with a single arrowhead:
>>──| The first line of a syntax diagram that is longer than one line |──>
>──| The continuation of the subcommands, parameters, or both |─────────><
Some diagrams might contain syntax fragments, which serve to break up diagrams that are too long, too complex, or too repetitious. Syntax fragment names are in mixed case and are shown in the diagram and in the heading of the fragment. The fragment is placed below the main diagram:
>>──| Syntax fragment |───────────────────────────────────────><
Syntax fragment:
|──1ST_OPERAND──,──2ND_OPERAND──,──3RD_OPERAND──|
This section summarizes the CARMA, Application Deployment Manager, SCLM Developer Toolkit, and other customization task information in IBM Rational Developer for System z Host Configuration Guide (SC23-7658). For more details, see that publication.
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 System z provides multiple pre-built RAMs, as well as source code examples for creating your own RAM.
The IBM Rational Developer for System z Interface for CA Endevor® Software Configuration Manager gives Developer for System z clients direct access to CA Endevor® SCM.
SCLM Developer Toolkit provides the tools needed to extend the capabilities of SCLM to the client. SCLM (Software Configuration and Library Manager) itself is a host-based source code manager that is shipped 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 legacy code development as well as 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.
Similar to the Developer for System z client, the Developer for System z host supports running code analysis tools, which are provided as a separate product, IBM Rational Developer for System z Host Utilities. A benefit of doing code analysis on the host is that it can be integrated in your daily batch processing.
This customization task does not require assistance, special resources, or special customization tasks.
Developer for System z clients version 8.0.1 and later pull client configuration files and upgrade information from the host when they connect, ensuring that all clients have common settings and that they are up-to-date.
z/OS Projects can be defined individually through the z/OS Projects perspective on the client or can be defined centrally on the host and propagated to the client of a user, as needed. These "host-based projects" look and function exactly like projects that are defined on the client except that their structure, members, and properties cannot be modified by the client, and they are accessible only when connected to the host.
External (client-host) communication can be encrypted using SSL. This feature is disabled by default and is controlled by the settings in ssl.properties.
This customization task does not require assistance, special resources, or special customization tasks.
Developer for System z supports different levels of tracing the internal program flow for problem solving purposes. RSE, and some of the services called by RSE, use the settings in rsecomm.properties to know the desired detail level in the output logs.
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 are parsed when a content assist operation is performed, regardless of whether that file or member was included in the source code using a preprocessor directive.
This customization task does not require assistance, special resources, or special customization tasks.
Remote Execution (REXEC) is a TCP/IP service to let clients execute a command on the host. Secure Shell (SSH) is a similar service, but here all communication is encrypted using Secure Socket Layer (SSL). Developer for System z uses either service for doing remote, host-based actions in z/OS UNIX subprojects.
This customization task does not require assistance, special resources, or special customization tasks.
Developer for System z supports the interpreting and expanding COBOL and PL/I include statements, including select third-party include statements. Developer for System z also provides a sample REXX exec, FEKRNPLI, that can be called by the Developer for System z client to expand PL/I source by starting the PL/I compiler.
This customization task does not require assistance, but does require the following resources or special customization tasks: LINKLIST update.
Frameworks that assist developers in writing code to perform repeatable, self-checking unit tests are collectively known as xUnit. Developer for System z provides such a framework for unit testing of Enterprise COBOL and PL/I code, called zUnit.
The Developer for System z Enterprise Service Tools (EST) component supports different formats of Arabic and Hebrew interface messages, as well as bidirectional data presentation and editing in all editors and views. In terminal applications, both left-to-right and right-to-left screens are supported, as well as numeric fields and fields with opposite-to-screen orientation.
Additionally, EST-generated code can support bidi transformation in environments other than CICS SFR; for example, batch applications. You can make the EST generators to include calls to the bidirectional conversion routines by specifying the appropriate bidi transformation options in the EST generation wizards and linking the generated programs with the appropriate bidirectional conversion library, FEK.SFEKLOAD.
The Developer for System z client has a code generation component called Enterprise Service Tools (EST). For code generated by EST to issue diagnostic error messages, all IRZ* and IIRZ* modules in the FEK.SFEKLMOD load library must be made available to the generated code.
The Developer for System z Integrated Debugger host component allows version 9.0.1 and higher clients to debug various Language Environment (LE) based applications, including CICS transactions loaded into read-only memory.
This customization task does not require assistance, special resources, or special customization tasks for the Developer for System z z configuration. However, there are requirements for the IBM Debug Tool for z/OS configuration.
IBM Debug Tool for z/OS provides a customized Language Environment (LE) user exit named CEEBXITA, which returns the TEST runtime options when called by the LE initialization logic in IMS and DB2 Stored Procedures. IBM Debug Tool for z/OS also provides the Debug Tool extension for the Problem Determination Tools Common Components server, to create and manage the TEST runtime options data set on the z/OS system. Developer for System z can use and enhance IBM Debug Tool for z/OS’s support for managing debug profiles for the IMS and DB2 Stored Procedure runtimes.
This customization task does not require assistance, special resources, or special customization tasks for the Developer for System z configuration. However, there are requirements for the IBM File Manager for z/OS configuration.
Some functions, such as unformatted QSAM editing, are part of regular data set handling by Developer for System z. More advanced functions, such as formatted data editing using copybooks or include files, require the IBM File Manager plug-in for Eclipse.
This customization task does not require assistance, special resources, or special customization tasks.
ISPF's TSO/ISPF Client Gateway and the SCLM Developer Toolkit function use the WORKAREA and /tmp directories to store temporary work files, which are removed before the session is closed. However, temporary output is sometimes left behind, for example, if there is a communication error while processing. For this reason, the WORKAREA and /tmp directories must be cleared periodically.
This section summarizes the information in IBM Rational Developer for System z Host Configuration Reference (SC14-7290). For more details, see that publication.
The Developer for System z host consists of several components that interact to give the client access to the host services and data. Understanding the design of these components can help you make the correct configuration decisions.
Developer for System z provides mainframe access to users on a non-mainframe workstation. Validating connection requests, providing secure communication between the host and the workstation, and authorizing and auditing activity are, therefore, important aspects of the product configuration.
Developer for System z 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 System z is not a monolithic application that can be identified easily to Workload Manager (WLM). Developer for System z consists of several components that interact to give the client access to the host services and data. Some of these services are active in different address spaces, resulting in different WLM classifications.
RSE (Remote Systems Explorer) is the core of Developer for System z. To manage the connections and workloads from the clients, RSE is composed of a daemon address space, which controls thread pooling address spaces. The daemon acts as a focal point for connection and management purposes, while the thread pools process the client workloads.
This makes RSE a prime target for tuning the Developer for System z setup. However, maintaining hundreds of users, each using 17 or more threads, a certain amount of storage, and possibly one or more address spaces requires proper configuration of both Developer for System z and z/OS.
z/OS is a highly customizable operating system. Sometimes, small system changes can have a huge impact on the overall performance. This chapter in the IBM Rational Developer for System z Host Configuration Reference highlights some of the changes that can be made to improve the performance of Developer for System z.
This chapter in the IBM Rational Developer for System z Host Configuration Reference contains information useful for a CICS Transaction Server administrator.
This chapter assists you with enhancing Developer for System z by writing exit routines.
This chapter assists you with mimicking a TSO logon procedure by adding DD statements and data sets to the TSO environment in Developer for System z.
Sometimes, multiple instances of Developer for System z must be active on the same system; for example, when testing an upgrade. However, some resources such as TCP/IP ports cannot be shared, so the defaults are not always applicable. Use the information in this chapter to plan the coexistence of the different instances of Developer for System z, after which you can use this configuration guide to customize them.
This section is provided to assist you with some common problems that you may encounter when setting up Secure Socket Layer (SSL), or during checking or modifying an existing setup. This section also provides a sample setup to support users authenticating themselves with an X.509 certificate.
This section is provided to assist you with some common problems that you may encounter when setting up TCP/IP, or during checking or modifying an existing setup.
© Copyright IBM Corporation 1992, 2013.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: 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 states 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 supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
Intellectual Property Dept. for Rational Software
IBM Corporation
Silicon Valley Lab
555 Bailey Avnue
San Jose, CA 95141-1003
U.S.A.
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.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
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-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
All 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 the names and addresses used by an actual business enterprise is entirely coincidental.
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.
Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:
© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. 1992, 2013.
If you are viewing this information in softcopy, the photographs and color illustrations may not appear.
IBM Software products, including software as a service solutions, (“Software Offerings”) may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering’s use of cookies is set forth below.
This Software Offering does not use cookies or other technologies to collect personally identifiable information.
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.
Applicability
These terms and conditions are in addition to any terms of use for the IBM website.
Personal use
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.
Commercial use
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.
Rights
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.