Upgrading

This milestone guides you through configuration of an upgrade to Strobe 18.02 from Strobe 5.2 or more current.

Tasks

Complete the following tasks to upgrade to Strobe 18.02.

Task 4.1 Allocate the Required Datasets and Provide Migration Information

1. Execute CLIST STRINCUS found in the hlq.SSTRSAMP dataset 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 following figure to create the $07ALSTR job.
   This job allocates the required Strobe datasets and Strobe startup procedures.
4. If your site is licensed for the Strobe for Db2/DDF option, replace DSN!!0.SDSNLOAD with the name of your site's most current Db2 version SDSNLOAD library.
5. Enter the high-level qualifier of the Strobe release that you are migrating from.
6. Enter the release number of the Strobe release that you are migrating from. Valid values are 18.02.00, 17.02.00, 16.03.00, 05.02.00, and 05.01.00.

7. Press Enter to continue. This information is used to create the migration JCL that will be used in Migrate Strobe Requests .

   Strobe JCL Customization Facility (Screen 2)

   

8. Edit and execute member $07ALSTR found in the hlq.SSTRSAMP dataset.
   $07ALSTR contains a job that creates the queue, log, system, group, and history datasets. This job also creates startup procedures STRBSM, STRBSSR, STRSSA, STRMSAS, and STRBMNAS.
9. Review the VOLSER and VOL=SER= values and, if required, supply a site-specific value.

Task 4.2 Migrate Strobe Requests

A new Strobe release may change the internal data structures of:

• Measurement requests
• AutoStrobe group requests
• AutoStrobe monitoring requests

These data structures reside on the Strobe queue, group, and AutoStrobe datasets. When they change for a new release, Strobe must create new queue, group, and AutoStrobe datasets. If you want to retain any of these existing requests for use with a new release of Strobe follow the procedures in this section. If you do not, you will need to manually resubmit the requests using the new Strobe release.

Task 4.2.1 Stop Strobe Session Manager

If the Strobe session manager is running, use the following MVS console commands to stop it:

• STOP STRBSM (production)
• STOP STRBMNAS <== If Global Monitoring is active

Task 4.2.2 Verify and Execute the $09MGSTR job

The $09MGSTR job is built using the input parameters you provided in Task-4-1-Allocate-the-Required-Datasets. If previous Strobe datasets are not found, you will be notified in the status panel above and the migration steps for that dataset will not be included in $09MGSTR.

The migration of the queue dataset is intended for all Strobe installations, including those with AutoStrobe. The migration of the group dataset and the AutoStrobe dataset is intended for AutoStrobe users only.

The following are brief descriptions of each of the migration steps that can be included in the $09MGSTR job. Please verify $09MGSTR has the correct steps and site-specific parameters depending on the datasets you intend to migrate to your new Strobe installation.

• If you want to migrate the queue dataset, these steps are included in $09MGSTR:
  • QUEUEXST: Checks to see if the new queue dataset exists. This is the dataset you are migrating to. If it does not exist, this step will allocate it.
  • QUEUEWRK: Allocates temporary work datasets used by the Strobe migration utility.
  • QUEUEMIG: Reformats the contents of the previous queue dataset and puts it on the new queue dataset. Doing so enables the new Strobe release to process the following types of requests from the previous release:
    • Queued and completed measurement requests
    • AutoStrobe monitoring requests

• If you want to migrate the group dataset, these steps are included in $09MGSTR:
  • GROUPXST: Checks to see if the new group dataset exists. This is the dataset you are migrating to. If it does not exist, this step will allocate it.
  • GROUPWRK: Allocates temporary work datasets used by the Strobe migration utility.
  • GROUPMIG: Reformats the contents of the previous AutoStrobe dataset and puts it on the new group dataset. This enables the new Strobe release to process the following types of requests from the previous release:
    • Queued and completed measurement requests
    • AutoStrobe monitoring requests

• If you want to migrate the AutoStrobe dataset, these steps are included in $09MGSTR:
  • AUTOXST: Checks to see if the new AutoStrobe dataset exists. This is the dataset you are migrating to. If it does not exist, this step will allocate it.
  • AUTOCREA: Attempts to copy the contents of the previous AutoStrobe dataset to the new queue dataset.
  • AUTOMIG: Synchronizes the new AutoStrobe dataset to the new queue dataset

Review the header comments in $09MGSTR that describe the steps included in the job. Submit $09MGSTR after you have verified these steps and that the parameters you have supplied are correct.

Task 4.3 Integrate Strobe with MVS

Task 4.3.1 Copy Runtime Libraries

Compuware recommends 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 4.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. Compuware 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. Bring down your current version of Strobe
2. Ensure that the members in the Strobe 18.02 hlq.SSTRAUTH library are in an APF-authorized library that is contained in the LINKLIST. Replace the modules from the earlier release.
3. Use the MVS MODIFY system command to refresh the system linklist:

Task 4.4 Implement the Strobe PARMLIB Under CMSC

Strobe parameters are managed by the Compuware Mainframe Services Controller (CMSC). The CMSC component is SMP/E-installed with Enterprise Common Components (ECC) as described in Milestone-1-Ensure-Installation-and-Configuration-of-Companion-Products. This address space is a centralized facility that provides Compuware 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 4.4.1 Strobe Parameter Migration

Previous Strobe release parameter members must go through a migration process. To prepare for this migration, depending upon the currently installed Strobe release from which you are migrating, the following actions should be taken:

• If you are migrating from Strobe Release 16.03 or less current, rename your existing Strobe parameter member to STRB00 and copy it to a dataset in the //CWPARM DD concatenation in the CMSC JCL, or ask your CMSC administrator to do so.
• Refer to the “Migration Utility” chapter in the Enterprise Common Components Advanced Configuration Guide for information about using the PARMLIB migration utility. This utility will migrate Strobe Release 16.03 or prior PARMLIB members to the current CMSC format.
• 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.
• For installations currently using CMSC, no action is required at this time.

Task 4.4.2 Strobe Parameters To Review

1. While most parameters have a default setting, the following parameters in the hlq.SSTRPARM library are site-specific and should be reviewed at installation time:
   • Set UI_STRBLOAD to the name of your hlq.SSTRLOAD dataset.
   • Set UI_STRBETXT to the name of your hlq.SSTRMSGS dataset.
   • Set UI_STRHIST to the name of the history dataset that was allocated by the HISTDS step of the $07ALSTR job.
   • Set UI_STRHISTA to the name of the history alternate index dataset that was allocated by the HISTDS step of the $07ALSTR job.
   • Set UI_STRHLOG to the name of the history log dataset that was allocated by the HISTLOG step of the $07ALSTR job.
   • Set the STRAUTO parameter to the name of your AutoStrobe dataset allocated by the AUTODS step of the $07ALSTR job.
2. 2.An additional sample Strobe parameter member, STRBALL, has been provided in the hlq.SSTRPARM library. This member contains an example of all Strobe parameters. Refer to the Advanced-Configuration-Guide for a complete description of installation parameters that control Strobe functions.

Task 4.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 4.5 Configure the Strobe for Db2 Options

Task 4.5.1 Bind Strobe Db2 Packages

Bind the Strobe Db2 Packages by completing the following steps:

1. Edit the SBDB2UPG 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.