Verifying product installation

This milestone provides instructions for verifying the Strobe installation.

Complete the following tasks to verify the Strobe installation.

Task 1 Start and Configure Strobe for Testing

Complete the following tasks to start and configure Strobe for testing.

Task 1.1 Start the Strobe Address Space

Start Strobe from the operators console by entering:

Task 1.2 Verify the Strobe CLIST

hlq.SSTRCLST data set member Strobe includes a TSO CLIST for executing Strobe/ISPF. The CLIST uses the ISPF/PDF LIBDEF service to allocate and concatenate application-level libraries.

The CLIST invokes the ISPF LIBDEF service to define panel, message, and skeleton libraries, executes the Strobe program STRBISPF, and invokes the LIBDEF service again to free the libraries when you exit.

By default, the CLIST uses the Simple Deploy method to allocate BMC data set names as specified with the SBNODE(PARMLIB) and the Enterprise Common Components (ECC) CMSC PARMLIB member DDSNnnnn. If you do not specify a DDSNSFX, the default DDSN00 member will be used. When using a different DDSN suffix, just update the DDSNSFX( ). For example, DDSNSFX(CPWR) points to DDSNCPWR.

The Simple Deploy method requires ECC Release 17.02, with all current maintenance applied. The comments in the member also provide instructions if you choose not to use the Simple Deploy method.

If you choose to use the simple Deploy method:

1. Ensure SBNODE(PARMLIB) is coded.
2. Verify that CMSC Simple Deploy PARMLIB member(s) DDSNnnnn have been updated with the DDNAMEs and data set names for your installed instance of the Strobe run-time libraries.

Use this CLIST in either of the following ways:

• Execute the CLIST from the command line of any ISPF/PDF panel:

TSO EXEC 'hlq.SSTRCLST(STROBE)'

• If desired, copy member Strobe to a library in your SYSPROC concatenation and modify your site's existing ISR@PRIM or equivalent panel to invoke the CLIST. 

  Warning

  Ensure the following:

  1. The &ZTRAIL = .TRAIL statement must appear in the PROC section of the ISR@PRIM or equivalent panel.
  2. Remember to reapply the Strobe/ISPF changes after performing any SMP/E maintenance.

Task 2 Measure a Sample Program

The Strobe hlq.SSTRSAMP sample library data set provides a batch job to run a test measurement session. The job creates a sample data set, lists the Strobe messages produced during the measurement session, and deletes the request. Submit member TESTSTR, shown in the following figure, to test the production version of Strobe from the LINKLIST:

Measure a Sample Program (Member TESTSTR)

Edit member TESTSTR as follows:

1. The &ZTRAIL = .TRAIL statement must appear in the PROC section of the ISR@PRIM or equivalent panel.
2. Remember to reapply the Strobe/ISPF changes after performing any SMP/E maintenance.
3. Edit the job control statements in TESTSTR as needed for your site and supply a JOB statement.
4. Change STROBE.SSTRLOAD to the name of your unauthorized Strobe Load Library.
5. Execute the job.

A return code 4 is acceptable.

Task 3 Create a Performance Profile

Complete the following steps to create a Strobe performance profile:

1. Access Strobe ISPF by entering TSO EXEC 'hlq.SSTRCLST(STROBE)'.
2. Enter 4 (PROFILE) in the Option field.
   The Strobe – Produce a Performance Profile panel is displayed.
3. Type F in the Option field to initiate Foreground Processing.
4. Type into the Sample Data set Name field the name of the Strobe sample data set that was created when you submitted the TESTSTR job.
   To find the name of the sample data set, execute the FIND command in the TESTSTR JES output for message STR6800I.
5. If not already selected, type T (Text Report) in the Output Format field.
6. Press Enter.
   Your Strobe Performance Profile is displayed.

Task 4 Verify Strobe for Db2/DDF and SQL Analysis

You can verify that Strobe Db2 measurement and SQL Analysis are operating and running correctly by creating a sample data set and viewing it using iStrobe. Two JCL members called STRANSMP and STRANSMI create a workload that you can measure and provide a sample data set to generate a Performance Profile for iStrobe. STRANSMI runs the STRANVER installation verification program. It executes STRANVER 50 times. You can edit the STRANSMI member to increase or decrease the Db2 workload by changing the number of RUN statements in it.

1. Edit member STRANSMP as follows:
   1. Change the CNTL value to the name of your Strobe sample library data set (hlq.SSTRAMP).
   2. Change the DB2LOAD value to the name of your Db2 load library that contains the DSNTIAR and connection modules.
   3. Change the STRBLIB value to the name of your unauthorized Strobe load library (hlq.SSTRLOAD) that contains the Strobe SQL Analysis load modules.
   4. Change the STRBAUT value to the name of your authorized Strobe load library (hlq.SSTRAUTH) that contains Strobe load modules.
   5. Change the SSID value to the ID of the Db2 subsystem against which you will run Strobe SQL Analysis.
   6. Change the PREFIX value to the high-level qualifier(s) of your Strobe sample library data set.
2. Execute the job.
3. Using the sample data set created by member STRANSMP, use Strobe/ISPF to create the iStrobe Performance Profile, as described in the Using-Strobe-to-measure-online-applications-and-batch-programs.
4. Download and view the measurement data with iStrobe.

Task 5 Create a Performance Profile with Indexed Source Support

Members DDIOCOB1 and DDIOCOB2 in the hlq.SSTSRAMP sample library data set are jobs that test Strobe with DDIO mapping. DDIOCOB1 should be modified to conform to your installation's compile and link procedure, and then used to compile and link a sample source program (SAMPLEW). The Strobe STRBSSR procedure performs the mapping function using your DDIO data set. After compilation, Strobe measures the test program and produces a sample data set. The DDIO file and sample data set are then used as input to job DDIOCOB2 to create a Performance Profile with indexed source support.

Before you configure:

1. Make the following edits to DDIOCOB1:
   1. Supply a JOB statement.
   2. Change STROBE.SSTRSAMP to the name of your Strobe sample library data set.
   3. Change PREFIX to the high-level qualifier name of the sample data set Strobe generates.
   4. Change BMCHLQ.LCXNNN.SLCXLOAD to the name of your BMC AMI Common Shared Services load library.
   5. Change BMCHLQ.CX.DDIO to the name of your DDIO file.
2. Execute the job.
3. Make the following edits to DDIOCOB2:
   1. Supply a JOB statement.
   2. Change STROBE.SSTRLOAD to the name of your unauthorized Strobe load library.
   3. Change BMCHLQ.LCXNNN.SLCXLOAD to the name of your BMC AMI Common Shared Services load library.
   4. Change BMCHLQ.CX.DDIO to the name of the DDIO file you compiled to in DDIOCOB1.
   5. Change PREFIX.JOBNAME.S001D001 to the name of the sample data set Strobe generated in DDIOCOB1.
4. Execute the job.

Members DDIOPLI1 and DDIOPLI2 provide the same functionality for testing a sample PL/I program. Member INDEXFOR provides similar functionality for testing a sample FORTRAN program without the use of DDIO. DDIOCOB1, DDIOCOB2, DDIOPLI1, DDIOPLI2, and INDEXFOR are included in the hlq.SSTRSAMP sample library data set.

Task 6 Test in a Sysplex Environment

If you installed Strobe on several systems within an MVS sysplex, you can first determine that Strobe is correctly functioning in the sysplex environment, and then verify that the Strobe version you are using recognizes the other systems where Strobe is installed:

1. When you start Session Manager as described in Start the Strobe Address Space and you have installed Strobe in a sysplex environment, ensure that the following messages appear in the Session Manager log:
   1. STR6169I Strobe environment is now created on system sysname (as member of XCF group xcfgroup)
   2. STR6402I Strobe-XCF group members are: localsysnamesysname1sysname2...sysnamenn
2. To verify that Strobe is installed on other systems in the sysplex and that Strobe on each system recognizes the other installed versions, perform the following steps after you install the ISPF panels and start Strobe:
   
   1. From the Strobe– Add Queued Request panel, clear the System field and press Enter.
      Strobe lists all systems contained within the sysplex where a version of Strobe is installed.
   2. Submit a request to measure a job on each system listed in the XCF-GROUP, and verify it is successfully measured.