Rational Developer for System z Server Health Checklist

Product documentation


Abstract

The IBM Rational Developer for System z (RDz) Server Health Checklist is a guide to aid with the installation and configuration of RDz. This document is a supplement and not a replacement for the existing RDz publications.

Content


Table of Contents:


Planning and prerequisites for RDz host installation



In preparation for RDz host installation and configuration, review the Rational Developer for System z Host Configuration Quick Start Guide and the Program Directory for IBM Rational Developer for System z for detailed instructions on the SMP/E installation of the product.

Review the list of z/OS host requisite products starting with the " z/OS Host Requisites" section of the Rational Developer for System z Prerequisites Guide.

Review Chapter 1, "Understanding Developer for System z", of the Rational Developer for System z Host Configuration Reference Guide to familiarize yourself with RDz component overview

The key requisites for a basic setup are:
  • z/OS 1.8 or higher
  • ISPF APAR OA38740 (TSO/ISPF Client Gateway)
  • Java 5.0 or higher (32-bit or 64-bit). Also, 64-bit version is recommended for higher addressability


Because of past issues with user ID switching in Java, this table shows the status of Java versions and service releases:

Java Version - Verified Service Release
1.5 latest SR
1.6 latest SR
1.601 latest SR
1.7 Not recommended



PARMLIB Definition


_____ (PARMLIB) Verify the required PARMLIB changes for a basic setup only are in place. These values can be checked and set dynamically (until the next IPL) with console commands:
  1. ___ Set MAXASSIZE in SYS1.PARMLIB(BPXPRMxx) to 2G.
  2. ___ Set MAXTHREADS in SYS1.PARMLIB(BPXPRMxx) to 1500 or higher.
  3. ___ Set MAXTHREADTASKS in SYS1.PARMLIB(BPXPRMxx) to 1500 or higher.
  4. ___ Set MAXPROCUSER in SYS1.PARMLIB(BPXPRMxx) to 50 or higher.



Security Definition


____ (FEKRACF) Customize and submit sample member FEKRACF in data set FEK.#CUST.JCL to create the security definitions for Developer for System z. The user submitting this job must have security administrator privileges, such as being RACF SPECIAL.

Note: For those sites that use CA ACF2 TM for z/OS or CA Top Secret® for z/OS, refer to your product page on the CA support site. Check for the related Developer for System z Knowledge Document. This Knowledge Document has details on the security commands necessary to properly configure Rational Developer for System z.


____ For a closer look at the RACF setup, have your security admin collect the output for these RACF commands or the equivalent command for the security package used by your site.
  • SETROPTS LIST
  • RLIST APPL FEKAPPL ALL
  • RLIST PTKTDATA FEKAPPL SSIGNON ALL
  • RLIST PTKTDATA IRRPTAUTH.FEKAPPL.* ALL
  • RLIST FACILITY BPX.SERVER ALL
  • RLIST FACILITY BPX.POE ALL


____ Verify PassTicket setup with the output from the previous step.
  1. ___ Verify existence of profile FEKAPPL in class APPL. If UACC is not (at least) READ, then verify if WARNING is set to YES or that server ID/everyone (*) has (at least) READ access
  2. ___ Verify existence of profile FEKAPPL in class PTKTDATA, best with UACC NONE
  3. ___ Verify that the application data field contains the string ‘NO REPLAY PROTECTION’ (there may be text before/after it) Also verify that the ‘secure sign on’ key is defined and is KEYMASKED
  4. ___ Verify existence of profile IRRPTAUTH.FEKAPPL.* in class PTKTDATA, best with UACC NONE
  5. ___ Verify that the profile is recognized as a generic profile (the (G) behind the profile name)
  6. ___ Verify that the server ID has (at least) UPDATE access, or that WARNING is set to YES
  7. ___ Verify that the APPL and PTKTDATA class are active. The list always starts with DATASET USER GROUP, after which it becomes alphabetical





Basic Customization




Once the SMP/E installation is complete and the product code and sample files have been copied to the target datasets, follow the steps below to configure and customize the core components of RDz.

There are various possible error messages that can occur while installing, customizing, and running Rational Developer for System z. Refer to the publication Answers to common host configuration and maintenance issues for the lists of most common messages, causes, and what you can do to correct the problem.

    ____ (SETUID) Insure the file system (HFS or zFS) in which RDz is installed is mounted with the SETUID permission bit on. This is the system default.

    ____ (SMP/E) Complete the SMP/E installation.

    ____ (FEKSETUP ) 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.

    _____ (JMON) 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 high-level qualifier of the load library, default FEK
    • The JES Job Monitor configuration file, default FEK.#CUST.PARMLIB(FEJJCNFG)

    _____ (RSED) 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 following code sample, you have to provide this information:
    • The home directory where Developer for System z is installed, default /usr/lpp/rdz
    • The location of the configuration files, default /etc/rdz

    _____ (LOCKD) Customize the sample started task member FEK.#CUST.PROCLIB(LOCKD), as described within the member, and copy it to SYS1.PROCLIB. As shown in the following code sample, you have to provide this information:
    • The home directory where Developer for System z is installed, default /usr/lpp/rdz
    • The location of the configuration files, default /etc/rdz

    ____ (FEKLOGS) Customize and run FEKLOGS which gathers UNIX log files and analyzes and interprets the UNIX-based configuration files. Sample job FEKLOGS is located in FEK.#CUST.JCL, unless you specified a different location when you customized and submitted job FEK.SFEKSAMP(FEKSETUP).


If you encounter an error during installation verification or while running the product, set "debug_level=2" property in the rsecomm.properties file and reproduce the error before running FEKLOGS to gather the logs. For more documentation on FEKLOGS, see the Rational Developer for System z Host Configuration Reference Guide.



IVP operator commands

    ____ Verify PassTicket reusability. Developer for System z requires that the PassTickets it generates are reusable, because PassTicket generation is limited to one per user per second. Verify PassTicket reusability by executing the following operator command. Replace userid with a valid TSO user ID.

    MODIFY RSED,APPL=IVP PASSTICKET,userid

    ____ Verify the RSE daemon connection by executing the following command. Replace userid with a valid TSO user ID.

    MODIFY RSED,APPL=IVP DAEMON,userid

    ____ Verify the ISPF Client Gateway connection by executing the following command. Replace userid with a valid TSO user ID.

    MODIFY RSED,APPL=IVP ISPF,userid





WLM and Tuning Considerations



____ Check the average CPU utilization on your system. Is it 90% or more?

As documented in “Workload classification” on page 59 of the Rational Developer for System z Host Configuration Reference Guide, RDz creates different types of workloads on your system. These different tasks communicate with each other, meaning the actual elapse time becomes important to avoid time-out issues for the connections between the tasks. As a result, RDz tasks should be placed in high-performance service classes, or in moderate-performance service classes with a high priority.

This table is a summary of the recommended Response Time goals and Velocity goals based on WLM considerations

Description Task name Workload Response time goals Velocity goals
JES Job Monitor JMON STC high-performance one-period velocity goal
Lock daemon LOCKD STC high-performance one-period velocity goal
RSE daemon RSED STC high-performance one-period velocity goal
RSE thread pool RSEDx OMVS high-performance one-period velocity goal
ISPF Client Gateway (TSO
Commands service and
SCLMDT)
<userid>x OMVS high-performance percentile
response time
TSO Commands service (APPC) FEKFRSRV ASCH high-performance percentile
response time
CARMA (batch) CRA<port> JES high-performance percentile
response time
CARMA (crastart) <userid>x OMVS high-performance percentile
response time
CARMA (ISPF Client Gateway) <userid> and <userid>x OMVS high-performance percentile
response time
MVS build (batch job) * JES high-performance percentile
response time
z/OS UNIX build (shell commands) <userid>x OMVS high-performance percentile
response time
z/OS UNIX shell <userid> OMVS high-performance percentile
response time
File Manager task <userid>x OMVS high-performance percentile
response time
Application Deployment Manager CICSTS CICSTS high-performance percentile
response time




Storage Usage



Java heap size limit

____ Review the information on maximum Java heap size and decide on initial values.

The maximum Java heap size is defined in rsed.envvars with the Xmx directive. If this directive is not specified, Java uses a default size of 512 MB (64 MB for Java 5.0). You should specify a value of 256 MB or higher. When running in 64-bit mode, Java will attempt to allocate the heap above the 2 GB bar, freeing up space below the bar.

The thread pool’s usage of the Java heap depends heavily on the actions done by the connected clients. Regular monitoring of the heap usage is required to set the optimal heap size limit. Use the modify display process operator command to monitor the Java heap usage by RSE thread pools.

The sample rsed.envvars setup aims for 30 users per thread pool:
  • maximum.clients=30
  • maximum.threads=520 (10+17*30 = 520, so 520 allows for 30 clients)


The sample rsed.envvars setup lets the Java heap grow up to 512 MB. This allows for 30 clients using an average of 17 MB per client (30*17 = 510).

As reference, this table shows values used in sample RDz environments for key rsed.envvars settings that impact storage usage:

xmx (maximum java heap) maximum.clients Region Size Primary type of
development
512M 30 PL/I
512M 10 1.3 GB COBOL
384M 12 COBOL
800M (64-bit) 20 Not specified




Monitoring



Monitoring RSE

    ____ Issue the MODIFY RSED,APPL=DISPLAY PROCESS operator command to display the RSE thread pool processes. The “Memory Usage” field shows how much of the defined Java heap is actually used.


Monitoring z/OS UNIX

    ____ Issue the DISPLAY OMVS,OPTIONS operator command to display the current values of z/OS UNIX directives that can be set dynamically.




Integration Scenarios Testing



Once you have gotten through the host installation and have run through the IVP process, you begin the workstation planning and installation process. You go through an exercise to confirm everything is working.

These are example checklists for verifying the host environment and configuration:






Reference Materials


Here are links to the documentation required for RDz host installation and configuration. For a complete list of available RDz documentation, see the Rational Developer for System z Library.




Original publication date

2013/6/11

Rate this page:

(0 users)Average rating

Document information


More support for:

Rational Developer for System z
Installation

Software version:

8.0.3, 8.5

Operating system(s):

z/OS

Reference #:

7038551

Modified date:

2013-06-11

Translate my page

Machine Translation

Content navigation