With Strobe 18.02 and iStrobe 19.01, Compuware continues to evolve the next generation of Application Performance Management (APM) on z/OS. The purpose of our next generation solution is to enable our customers to proactively identify, understand, and act upon emerging performance problems in order to be successful in achieving their APM goals.
Note: Strobe Release 18.02 requires Enterprise Common Components (ECC) Release 17.02 or more current, with all current maintenance applied . Click the following link for access to ECC current maintenance: https://go.compuware.com/products/cy/fixes/30240.aspx .
The Strobe hlq .SSTRCLST library start-up CLIST member STROBE has been updated to use the Simple Deploy method. This member allocates Compuware dataset names as specified with the SBNODE(PARMLIB) and the Enterprise Common Components (ECC) CMSC PARMLIB member DDSN nnnn . If you do not specify a DDSNSFX, the ECC hlq. SLCXCNTL library default DDSN00 member will be used. Refer to the Enterprise Common Components Installation and Configuration Guide and the Strobe Installation and Configuration Guide for more information at https://go.compuware.com .
Compuware has enhanced the Compuware PARMLIB parameter processing, including centralized parameter validation. Additionally, some parameters for the Compuware products were changed to reduce their complexity and make them easier to understand and configure. With this cumulative maintenance these changes have been incorporated into the sample parameter members that are supplied in the target sample library.
Enterprise Common Components (ECC) PTF CXS373A provides a parameter migration utility to assist with updating any existing Compuware parameter members at your site. Refer to the Release 17.02 Enterprise Common Components Installation and Configuration Guide for more information about using this utility.
This Rolling 4 Hour Average report allows the user to dynamically change the date range using the time axis. This redraws the graph to represent that time. When the graph plots show the hourly level, the user can click the plot and navigate to the MSU over time for all the displayed LPARs.
Date filtering can use an inclusive range. Numeric fields (such as CPU, EXCP) also contain an inclusive range. The filters can also be used by specifying only one of the boundaries in the range. This will, in effect, be a greater than (>) sign when using lower boundary, or a less than (<) sign when using the upper boundary. Positional wildcarding (?) can be used for alphanumeric fields to limit the values displayed in the filter selection.
Positional wildcarding is now available to Global Monitoring criteria (requires additional Strobe 18.02 ptf). It can be used for both the Include and Exclude criteria, allowing users to incorporate their naming conventions into Global Monitoring criteria.
The Strobe Installation and Configuration Guide has been rewritten and simplified for Release 18.02 to focus on the actual tasks required to install, configure, and customize a Strobe new installation or perform an upgrade on an existing installation. A second, newly created manual, the Strobe Advanced Configuration Guide, includes more specialized configuration and customization information previously contained in the original installation guide. These new guides are available on the FrontLine Strobe documentation site at https://go.compuware.com.
Compuware has enhanced the Common PARMLIB processing controlled by the Compuware Mainframe Services Controller (CMSC), including centralized parameter validation. These changes have been incorporated into the sample parameter members STRBALL, STRB00, and STRT00 in the Strobe hlq .SSTRPARM library. To effect these changes, Enterprise Common Components 17.02 is required with current maintenance applied.
When a Profile containing Notes is exported, it creates both a profile.xml and a notes.xml file. Then, when importing a Profile with the Notes, you will use the ZIP file created that contains both the profile.xml and notes.xml files.
Additional myStrobe filters are introduced to facilitate quicker results. Owner ID and LPAR are now specific for those two columns. This allows a user to quickly narrow the result to a specific user (Owner ID) to find their profile reports.
There is now a preference that can be used to eliminate the IBM CICS Supplied Transactions from the reports. When set to "Off", the IBM CICS Supplied Transactions will not display in the profile reports or the insight reports. This allows the user to focus on the application transactions in the reports.
With Release 18.02, to simplify the installation process for new Strobe installations, the STRB00 and STRT00 members have been modified to only include parameters that should be evaluated at installation time. A new member STRBALL has been provided as a reference point for all other Strobe parameters. Refer to the Strobe installation guide for the complete list of Strobe Release 18.02 parameters with their descriptions, options, and defaults.
Strobe Global Monitoring has been enhanced to provide additional statistics for improved diagnostics. New Global Monitoring parameters using the MVS MODIFY command have been added for generating CICS, IMS, and Global Monitoring Data Pump statistics. Global Monitoring SMF data control parameters have also been added for use with the MVS MODIFY command. Refer to the Strobe installation guide for more information.
Security, Users, Roles, and Groups have been removed from iStrobe and consolidated under Compuware Enterprise Services. They are located under the Compuware Enterprise Services Administration Security feature.
The Measurement Request and Profile reports are separated as they depict different entities. Datatable column headings are relevant to each grouping with each table having independent sorting. Today, users use Strobe ISPF for the status listings. This redesign allows customer’s to move their users out of Strobe's ISPF version and into iStrobe.
The Baseline feature allows users to create average times in the Totals columns for those profiles included in the baseline. The resulting baseline can then be used within myStrobe to compare the totals.
Strobe Release 18.02 introduces Embedded Source Support (ESS), available with Compuware Shared Services (CSS). CSS is SMP/E installed with Enterprise Common Components (ECC) and requires Release 17.02 for Embedded Source Support. The CSS COBOL Language Processor (LP) new ESS command for COBOL Version 5.1 and more current stores the COBOL compiler listing and other program data, not in a VSAM or sequential DDIO file, but instead in ESS records in the executable binary, the actual load module.
Compuware source solutions have been changed to first look for the ESS records and if found will not search for any DDIO file. However, if the ESS records are not found, the usual DDIO file search mechanism, as currently implemented in Strobe, will be used.
Refer to the Compuware Shared Services User/Reference Guide, Release 17.02 version, for more information about Embedded Source Support. Download this guide from the ECC products documentation site at https://go.compuware.com.
Programs are running on zIIPs via SRBs and other technological advances have necessitated changes in how Strobe works. The DIE (disabled interrupt exit) is utilized to obtain more accurate information, which includes SRB and enclave data. New reports in Strobe have been created to show SRB activity within the measured address space. These reports are available only within the Strobe wide profile report.
iStrobe has added a new Insight report named CICS Transaction Utilization. This report allows the performance analyst to specify a date range and a benchmark period of time. The report will then display the deltas for that date comparison for Service Units/Transaction, Transaction Count, and Total Service Units. This additional information is useful for the analyst to identify the overall affect over a period of time.
For Strobe software and hardware requirements, refer to the Strobe Installation and Configuration Guide on the Compuware Support Center website at https://go.compuware.com.
For iStrobe software and hardware requirements, refer to the Compuware Web Products Installation and Configuration Guide on the Compuware Support Center website at https://go.compuware.com.
Refer to the Compuware Product Currency Tables at https://frontline.compuware.com/apps/oscharts/zos.aspx for the associated End of Support dates.
• A Google Chrome security update prohibits viewing of WebHelp when the help is deployed locally from a file server (as opposed to a Web server). Attempting to view locally deployed help displays a blank help window. Compuware suggests that online help be viewed using Internet Explorer. Alternatively, Chrome's security feature can be turned off by launching Chrome with the command line option --allow-file-access-from-files. This method should only be used when opening local WebHelp that you trust.
Uncaught SecurityError: Blocked a frame with origin "http://<myMachine.fullyQualified.domain>:<port>" from accessing a frame with origin "http://<myMachine>:<port>". Protocols, domains, and ports must match.
• When running CES, iStrobe, Fault Analytics, and/or TJP in a Java environment that uses hardware encryption, the user ID under which CES runs will require authorization to execute the following CSFSERV functions:
• When installing iStrobe on Windows, you may encounter an error referring to the Java VM. This is a problem with InstallAnywhere and Java 8. It can be resolved by removing the following entry from the Path variable:
• If you specify a temporary directory smaller than that which is required for installation, you may be presented with a message indicating that your evaluation period has expired. You can reallocate space and restart the installation process.