Configuring after installation

This milestone guides you through configuration of a Strobe new installation.

Tasks

Task 3.1 Allocate the Required Data sets

1. Execute CLIST STRINCUS found in the hlq.SSTRSAMP data set to access the Strobe JCL Customization Facility as shown in the following figure.

2. Press Enter to continue.

   Strobe JCL Customization Facility (Screen 1)

   

3. Complete the fields in the following figure to create the $07ALSTR job.
   This job allocates the required Strobe data sets and Strobe startup procedures.
4. If your site is licensed for the Strobe for Db2 option, replace DSN!!0.SDSNLOAD with the name of your site's most current Db2 version SDSNLOAD library.
   Because you are performing a first-time installation, ignore the next three fields regarding a previous release because they apply only to upgrading a Strobe release.

5. Press Enter to continue.
   

   Strobe JCL Customization Facility (Screen 2)

   

6. Edit and execute member $07ALSTR found in the hlq.SSTRSAMP data set.
   $07ALSTR contains a job that creates the queue, log, system, group, and history data sets. Strobe expects the low level qualifier (LLQ) to remain as specified in the created JCL as shipped. This job also creates startup procedures STRBSM, STRBSSR, STRSSA, STRMSAS, and STRBMNAS.

7. Review the VOLSER and VOL=SER= values and, if required, supply a site-specific value. 

   Warning

   Although we do not recommend it, if your site standards require modifications to the Strobe started task names, the following changes must be made:

   1. Update the procedures (created by the $07ALSTR job) in the system procedure library to the new names.
   2. Ensure the Security steps in Task 3.2 Review external security considerations reflect the new names.
   3. Update the Strobe parameters MSASPROCNAME, SSAPROCNAME, and MNASPROCNAME in Strobe parameter member STRB00 to reflect the correct procedure names.

Task 3.2 Review External Security Considerations

Task 3.2.1 Strobe Started Tasks

Your site’s z/OS security administrator should review and implement the following security requirements:

1. The STRBSM started task requires a user ID defined to your security product and ALTER access to the Strobe Log data set. The Session Manager must be able to read and write to the Strobe Queue, System Message and Request Group data sets. For the Strobe Log data set, the session manager must have WRITE access and be able to create a data set (when Log data sets defined as GDGs). To use the automatic Performance Profile option, the session manager must have the authority to:

   1. Submit jobs on behalf of any Strobe user.
   2. Read sample data sets created by any Strobe user.
   3. Create a print file on behalf of any Strobe user.

   For z/OS systems, the Session Manager address space must also have UPDATE access to the BPX.SERVER profile in the FACILITY class so that Strobe can display the USS processes on the Active Process Section List panel. The Session Manager Address Space must have a UID of zero (UID(0)) specified in the rules of the security package (RACF, CA Top Secret, CA ACF2) you are using. This rule gives Strobe the authority to collect process information for all processes. For more information, refer to the IBM manual z/OS UNIX System Services Planning.

   To enable the Strobe Session Manager (running as a superuser) to successfully call the z/OS UNIX System Service BPX1SEU, define user BPXROOT to RACF, ACF2, or CA Top Secret. This action prevents Strobe from issuing message STR6429W.

   Always define the Strobe Session Manager to CA ACF2 as a Multiple-User Single Address Space System (MUSASS).

2. The STRMSAS started task requires a user ID/ACF2 logon ID defined to your security product; and if using RACF, it must have a RACF ID in the RACF started task group. Create an associated owner ID with an OMVS segment to allow use of TCP/IP for communications for the MSAS. Sample data sets are dynamically allocated and cataloged from this address space. Define any prefix used for the sample data sets to be allocated, read, written, and cataloged from the MSAS.
   Upon measurement initiation, the MSAS started task creates a data set and requires authority of ACC(ALL) if using CA Top Secret or ALTER access under RACF. The data set name is composed of two Strobe parameter values found in the hlq.SSTRPARM library, plus the job name of the job being measured.

   DSNAME=TSOESA /* SAMPLE DATASET NAME PREFIX */
   
   DSNSUFX=ACME1 /* SAMPLE DATASET NAME SUFFIX */

   Use DSNAME= to specify the first node of the data set name and DSNSUFX= to specify the last node of the data set name. If the measured job name is ABC1234Z, then ABC1234Z is used as the second level node for the data set name.

3. The STRSSA started task requires a user ID/ACF2 logon ID defined to your security product; and if using RACF, it must have a RACF ID in the RACF started task group (required for Strobe for Db2 licensed users).
4. The STRBMNAS started task requires a user ID/ACF2 logon ID defined to your security product; and if using RACF, it must have a RACF ID in the RACF started task group. Create an associated owner ID with an OMVS segment to allow use of TCP/IP for communications for the MNAS.

Task 3.2.2 User IDs

1. Any user ID that plans to generate Strobe Performance Profiles requires ALLOCATE, READ, WRITE, and CATALOG access to the sample data set naming conventions, similar to the STRMSAS started task.
2. Strobe users require READ access to the Strobe Log data set and the Strobe unauthorized load library (hlq.SSTRLOAD). They must also be able to read and write to the Strobe History and AutoStrobe data sets.
3. To further control user access to Strobe refer to the section entitled “Configuring Access Filter Security” in the Advanced-Configuration-Guide. This security interface allows you to control security considerations such as the following:
   • Who can use Strobe to measure jobs
   • Systems on which those measurement requests can run
   • Whether users can measure any job or just their own
   • Who is authorized to start Strobe as a batch job
   • Who has privileges to administer Strobe

Task 3.3 Integrate Strobe with MVS

Task 3.3.1 Copy Runtime Libraries

We recommend that copies of selected SMP/E target libraries be made that will comprise the runtime environment. The SMP/E target libraries listed in the following table are recommended to have corresponding runtime copies.

Task 3.3.2 Authorize and Add the Strobe SSTRAUTH Library to the System LINKLIST Concatenation

To establish the Strobe environment, some Strobe modules must execute in an authorized state. BMC has provided a load library, hlq.SSTRAUTH, that contains those modules. APF-authorize only the hlq.SSTRAUTH library. To perform this task, complete the following steps:

1. Ensure that the members in the Strobe 21.01 hlq.SSTRAUTH library are in an APF-authorized library that is contained in the LINKLIST.
2. Use the MVS MODIFY system command to refresh the system linklist:
   MODIFY LLA,REFRESH

Task 3.4 Implement the Strobe PARMLIB Under CMSC

Strobe parameters are managed by the BMC AMI Common Mainframe Services Controller (CMSC). The CMSC component is SMP/E-installed with Enterprise Common Components (ECC) as described in Installing-and-configuring-companion-products. This address space is a centralized facility that provides BMC Common parameter library services. This facility functions in a similar manner to the IBM z/OS PARMLIB. Strobe requires CMSC to be installed for all Common PARMLIB processing.

Task 3.4.1 Create PARMLIB Member STRB00

In order to use the CMSC component, copy the Strobe parameter data set member STRB00 from the hlq.SSTRPARM library to a data set in the //CWPARM DD concatenation in the CMSC JCL, or ask your CMSC administrator to do so.

Task 3.4.2 Review Strobe Parameters

1. While most parameters have a default setting, some parameters in the hlq.SSTRPARM data set are site-specific and should be reviewed at installation time:
   • Set SSA=NO if your site is not licensed for the Strobe for Db2 options.
   • Set UI_STRBLOAD to the name of your hlq.SSTRLOAD data set.
   • Set UI_STRBETXT to the name of your hlq.SSTRMSGS data set.
   • Set UI_STRHIST to the name of the history data set that was allocated by the HISTDS step of the $07ALSTR job.
   • Set UI_STRHISTA to the name of the history alternate index data set that was allocated by the HISTDS step of the $07ALSTR T(est) job.
   • Set UI_STRHLOG to the name of the history log data set that was allocated by the HISTLOG step of the $07ALSTR job.
   • Set the STRAUTO parameter to the name of your AutoStrobe data set allocated by the AUTODS step of the $07ALSTR job.
   • The last line in the new parameter member is $$$ V2 END $$$ -- DO NOT MODIFY OR REMOVE. This line marks the end of new format and must not be modified or removed.
2. If you changed your Strobe started task names in Strobe Started Tasks, ensure that MSASPROCNAME, SSAPROCNAME, and MNASPROCNAME parameters reflect the correct names.

3. An additional sample Strobe parameter member, STRBALL, has been provided in the Strobe hlq.SSTRPARM library. This member contains an example of all Strobe parameters. See Advanced-Configuration-Guide for a complete description of installation parameters that control Strobe functions. 

   Warning

   The STRB00 parameter member contains only the most commonly changed parameters. If you changed the MNASPROCNAME started task name, you must add the parameter to your STRB00 member. An example of this parameter is in the sample parameter member STRBALL.

Task 3.4.3 Update CMSC with STRB00

Use the z/OS MODIFY (F) command to update the CMSC with the PARMLIB members you created.

Refreshing a Single Parameter Member

F cmscname,PARMLIB REFRESH member_name

Task 3.5 Configure the Strobe for Db2 Options

Task 3.5.1 Bind Strobe Db2 Packages and Plan and Grant Required Privileges

Bind the Strobe Db2 Packages and Plan and Grant Authorization by completing the following steps:

1. Edit the SBDB2INS JCL member found in hlq.SSTRSAMP and make the changes as directed in the JCL.
2. Submit the JCL.
3. Repeat the steps for each Db2 subsystem where Strobe measurements will occur.

Task 3.5.2 Create Db2 Explain Tables

Before you can create a Performance Profile for Strobe that contains Strobe SQL Analysis reports, a PLAN_TABLE, DSN_FUNCTION_TABLE, DSN_PREDICAT_TABLE, and DSN_STAT_FEEDBACK (optional DSN_QUERYINFO_TABLE if used at your site) must exist for the resolved or secondary authorization ID of the user/job running the reports.

Sample DDL to create the Explain tables is in the IBM Db2 SDSNSAMP library in member DSNTESC. The DDL for the DSN_STAT_FEEDBACK table, used for additional reporting, exists only in Db2 Version 11 and more current. The table qualifier must match the authorization ID of the user executing reports.

For support of Db2, Strobe requires z/OS Unicode Services and the appropriate Unicode conversion tables. If these Unicode conversion tables are not installed on your z/OS system, your Strobe for Db2 and SQL Analysis reports might be unreadable.

Verify that you have installed the following Unicode conversion tables on your system, by issuing the MVS Display command D UNI,ALL:

• Strobe installer
• z/OS security administrator
• z/OS system programmer
• Db2 database administrator
• 01200-01208-E or -ER
• 01208-01200-E or -ER
• 01200-nnnnn-E or -ER, where nnnnn is the value of the SCCSID keyword in the DSNHDECP module of your Db2 subsystem

For general information about setting up a conversion environment and installing Unicode conversion tables, refer to the IBM z/OS Library. In particular, see z/OS Support for Unicode ™ (SA 22-7649), which specifies using the tables above as the base for conversion services.