Configuring Additional Product Options

This section provides instructions for configuration tasks not included in the Installation-and-Configuration-Guide.

The Strobeadministrator is required for these tasks.

Complete any of the following tasks that are required at your site:

7.1: Strobe for z/OS UNIX System Services
7.2: Configure Strobe for Natural/Adabas
7.3: Configure Strobe for Java and WebSphere Application Support
7.4: Configure Strobe for WebSphere MQ
7.5: CICS System Task Table
7.6: Using Strobe with OMEGAMON
7.7: Dynatrace Integration
7.8: Strobe for CA Gen (AllFusion) CA Panexec

Task 7.1:Strobefor z/OS UNIX System Services

You must enable SMF type 92 records for Strobeto collect z/OS UNIX System Services data.

You can use an MVS system IEFU85 exit program to avoid recording excess SMF 92 data. The Strobesample library contains a member, IEFU85, which shows an example of this exit.

To be able to measure a Webserver address space, you must add the Strobeload library to the RACF program control list. You must also ensure that the Compuware Shared Services (CSS) hlq.SLCXAUTH authorized load library is APF-authorized.

Task 7.2:Configure Strobefor Natural/Adabas

This section is designed to guide you through configuring the support for Natural/Adabas in Strobe.

Natural/Adabas StrobeParameters

To use Strobefor Adabas/Natural, you must edit the StrobePARMLIB member to supply the STRBANCE_TSO, STRBANCE_BATCH, STRBANCE_CICS, and STRBANCE_IMS parameters.

Parameter syntax

STRBANCE_TSO                    Natural Information for TSO

  NUCNAME=
  RELEASE=
END
STRBANCE_BATCH                   Natural Information for Batch
   NUCNAME=
   RELEASE=
END
STRBANCE_CICS                    Natural Information for CICS
   NUCNAME=
   TCMNAME=
   RELEASE=
END
STRBANCE_IMS                      Natural Information for IMS
   NUCNAME=
   NIINAME=
   RELEASE=
END

REDEFINE and PERMIT Keywords

This Keyword	Defines:
NUCNAME	The 8-character Natural nucleus name
NIINAME	The 8-character Natural/IMS interface module name, if the Natural nucleus executes in an IMS environment. This name is NIIvrmxx, where vrm is the Natural version, release and modification level (for example, 824) and where xx is the module name using the following conventions: IF - the Natural/IMS main interface module BM - the Natural/IMS batch message program (BMP) front-end OB - the Natural/IMS message-oriented (NTRD) front-end FR - the Natural/IMS conversational message processing program (MPP) front-end NC - the Natural/IMS non-conversational message processing (MPP) front-end
TCMNAME	The 8-character system control block module name, if the Natural nucleus executes in a CICS environment. This name is ncipCB, where ncip is the value of the parameter PREFIX in the Natural/CICS parameter module.
RELEASE	The 3-digit release number of the Natural nucleus, without the intervening periods (for example, enter 824 for release 8.2.4)

In addition, you must code an entry for the Adabas/IMS interface, ADALNI. ADALNI is an Adabase interface to access the Natural and Adabase user files. The Adabas/IMS interface module ADALNI is used In terminal-driven, dialog-oriented environments. In all other environments, the Adabas batch interface module ADALNK is used. Refer to the Software AG Natural/Adabase installation documentation for additional information about ADALNI.

Compuware provides an internal set of parameters that are loaded when no parameters are supplied in the PARMLIB member. These are not meant to be used for normal processing and must be replaced by the user because Natural attribution using these defaults will produce no information.

STRBANCE_TSO                     Natural Information for TSO
NUCNAME=TSONUC
RELEASE=999
END
STRBANCE_TSO                     Natural Information for TSO
NUCNAME=SHARENUC
RELEASE=999
END
STRBANCE_BATCH                   Natural Information for Batch
NUCNAME=BATCHNUC
RELEASE=999
END
STRBANCE_BATCH                   Natural Information for Batch
NUCNAME=SHARENUC
RELEASE=999
END
STRBANCE_CICS                    Natural Information for CICS
NUCNAME=CICSNUC
TCMNAME=CICSYSCB
RELEASE=999
END
STRBANCE_CICS                    Natural Information for CICS
NUCNAME=SHARENUC
TCMNAME=CICSYSCB
RELEASE=999
END
STRBANCE_IMS                     Natural Information for IMS
NUCNAME=SHARENUC
NIINAME=NII999IF
RELEASE=999
END
STRBANCE_IMS                     Natural Information for IMS
NUCNAME=SHARENUC
NIINAME=NII999BM
RELEASE=999
END

Task 7.3: Configure Strobe for Java and WebSphere Application Support

Java and WebSphere Application Server support in Strobeis provided by Compuware’s Topaz for Java Performance product. No Strobeconfiguration or customization is required to initiate a Topaz for Java Performance measurement. Refer to the Topaz for Java Performance user documentation on the BMC Support Center website or more information about installing and using Topaz for Java Performance support for Java in Strobe.

Strobecan optionally provide Java and WebSphere Application support using the Dynatrace product. Refer to the Dynatrace user documentation for more information about installing and using Dynatrace.

Task 7.4 Configure Strobefor WebSphere MQ

If your site is using Strobefor WebSphere MQ, you can identify a common user module in your site’s environment that applications call to access MQSeries. If you specify a common user module, it must be one of the following:

Separate load module from the load modules that invoke it
Separate CSECT in the program being measured
CSECT in one of the load modules that is mapped for measurement.

The common user module must comply with standard MVS linkage conventions as follows:

During its entire operation, register 13 of the common user module must point to its own save area.
Offset 4 (the second word) of that save area must point to a save area of the caller of the user module.
Offset 12 (the fourth word) of the caller’s save area must contain the return address to the calling routine.

Task 7.5 CICS System Task Table

If you are using Strobefor CICS to measure CICS transactions, you can specify whether a transaction is to be detailed. Strobeuses a table called the system task table to determine which transactions are initiated by the CICS system instead of user applications. If a transaction is listed in the table, Strobedoes not provide attribution for it or profile it.

At times, you may want Strobeto measure a system transaction. If a system transaction is used to broadcast messages to CICS users’ terminals, you can remove the name of the transaction from the table or you can add transactions to the table. If you are using a third party product and its transactions are appearing in the Performance Profile reports, you can add the transaction names to the table and Strobewill not attribute or profile them.

The CICS System Task Table is located in the member named UM0CTSK in the hlq.SSTRSAMP Strobesample library dataset. You can find the sample source in member @TRBCTSK in the sample library.

Task Description

Edit the table as follows, using the same format as shown in the example:

To add a transaction to be excluded for measurement, specify its four-character name following TRANID=.

If you add a transaction name, the name must be placed in the list in ascending (top to bottom) alphabetical order. For example, to add a transaction named CCYZ to the example table, you would add the specification between transaction names CCU2 and CDBC.

To remove a transaction from the table causing Strobeto measure it, delete the entire line from the table that specifies its name.
To enable Strobeto access the table and use it to determine which transactions to measure, SMP/E RECEIVE and APPLY the customized UM0CTSK USERMOD.

Task 7.6: Using Strobewith OMEGAMON

Strobemeasurement requests can be triggered using IBM’s OMEGAMON system monitoring software.

To integrate Strobewith OMEGAMON, you must define what is known as a situation using the Situation editor in the Tivoli Enterprise Portal (TEP). A situation is a logical expression of a condition to test. It can be used to raise alerts of certain conditions and to trigger single-action commands.

After defining the formula for a situation, you can specify an action to be taken when the situation (as defined by the formula) becomes True. The specified action can be to execute a system command. For Strobeintegration, the applicable system command is to start a cataloged procedure named STRBADD. This procedure initiates an ADD ACTIVE measurement request for the job that caused the situation to become True. The STRBADD procedure can be found in the SSTRPROC library created during Strobeinstallation.

The following is an example of the formula for a situation:

Job Name == TESTJOB1 AND Job CPU Time >= 1.00

It is possible that a formula using equal (==) for CPU time — or other numeric values — may never become True. Compuware recommends you use greater than or equal (>=) as shown in the example above.

The following is an example of a system command to be executed when the situation becomes True:

S STRBADD,J= &{Address_Space_CPU_Utilization.Job_Name}

Task 7.7: Dynatrace Integration

Strobecommunicates with the Dynatrace server to collect Java information. In order to do this, the user ID associated with the Measurement Services Address Space (MSAS) must have authority to use TCP/IP for communication, which requires an OMVS segment.

If you plan to use Dynatrace for Java support with Strobe, refer to the Dynatrace documentation for the system requirements.

Task 7.8: Strobefor CA Gen (AllFusion) CA Panexec

Strobefor CA Gen (AllFusion) CA Panexec supports job libraries and LINKLIST libraries managed by the CA Panexec product. To give Strobeaccess to control section information from the program libraries, you need to modify one of the Panexec modules. Member PANEPTF of your Strobe sample library dataset contains instructions on how to use the CA Panexec PTFs and control statements to install the change.

Ensure that the Panexec PTFs listed in the instructions have been applied to your CA-Panexec system.