Milestone 4 Configure Performance Test—Upgrade
This topic will guide you through the configuration of an upgrade to Performance Test 17.02.
If you are performing a new installation instead, skip ahead to Milestone 5 PARMLIB Implementation.
Complete the following tasks to upgrade to Performance Test 17.02.
Task 4.1: Run the Guided Configuration Dialog
Task 4.1.1: Launch the Guided Configuration Dialog
To launch the Guided Configuration, execute the $$$SETUP EXEC.
On the Command line, type TSO EX followed by the fully-qualified .INSTALL library name and REXX EXEC member name.
Task 4.1.2: SMP/E Installation Data Import
Specify the data set name where the BMC installer created the SMP/E ISPF tables. This will inform the Performance Test customization facility about the installation SMP/E environment. When the Install Data Import completes, the Product Suite Guided Configuration Panel is displayed as shown in the following figure.
Product Suite Guided Configuration screen
Option ===>
Performance Test FMID: MQQF170
Please complete required selections 2 through 6, in order, to
configure Performance Test
1 Import Parm Settings Get customization information from a prior install
2 Generate JCL Samples Generate JCL samples for product usage
3 Product Configuration Select and run automated customization tasks
4 Generate Manual Tasks Create non-product install task instructions based
on selections/values set in "Product Configuration"
5 Track Manual Tasks Non-product install task tracking checklist
6 Parmlib Gen Create parmlib sample using selections and values
set during "Product Configuration" tasks.
7 Apply Maintenance Receive and apply Performance Test sysmods
Task 4.2: Import Parameter Settings
If your site used the Guided Configuration dialog in a prior installation of Performance Test, you can import parameters and other customization data from your previous customization database into your new one.
Run option 1 Import Parm Settings to initiate the data import. The Import/Migrate Configure Settings screen will be displayed. Specify the name of the .INSTALL library from which to import the information.
Task 4.3: Generate JCL Samples
Run option 2 Generate JCL Samples to update product sample JCL and PROC members with the data set names of your SMP/E target environment. The members will be placed into the .INSTALL library.
Task 4.4: Product Configuration
Run option 3 Product Configuration. The Select Products & Features to Configure screen will be displayed, showing products and features available for configuration. Enter a slash (/) next to the products and features you want to configure. Press Enter after making your selections to advance to the Configure Products screen.
Task 4.5: Configure Products
The Select Products & Features to Configure screen allows you to select guided configuration tasks by product being configured: Performance Test for VTAM, Performance Test for Mainframe Servers, and/or Performance Test for IBM MQ. In turn, select each product to configure. For each selected product, a list of automated customization tasks is displayed, based on your set of selections on the Select Products & Features to Configure screen. Some customization tasks apply to more than one product and will appear in the task list for each of the products to which they apply. These tasks only need to be completed once.
Select each configuration task. The information requested on the screen may be pre-filled with imported input field data that you may accept or alter. Although data set names pre-filled with imported data are usable in this new version of Performance Test, they can be changed if desired. Some of the task screens will instruct you to use the GENERATE command to initiate a process after filling in the input fields. The configuration tasks may allocate data sets (or simply register them in the customization database when they already exist), tailor procs, build sample members, etc. They will also store information into a customization database within the .INSTALL library.
As you exit each task, a Set Task Status window is displayed where you can either indicate the status of the task as being Complete or, if you must collect information about a task, set the status to In Progress or Pending. This will help you re-visit the tasks after having collected the requisite information.
After completing all the automated product configuration tasks, return to the Product Suite Guided Configuration Screen to advance to the next subtask.
Task 4.6: Generate Manual Tasks
Run option 4 Generate Manual Tasks. This process will create five members with specific tasks—based on information from the preceding steps—to configure your system for use with Performance Test. Most, but not all, of the tasks will require no action because they were already done during a previous installation.
The names of these members tell you the area to which each task applies:
- TSKCICS
- TSKIMS
- TSKMVS
- TSKSECUR
- TSKVTAM.
The Performance Test installer should review these members to confirm which tasks need no action and which must be done, then distribute them as needed to system specialists to be completed.
The Generate Manual Tasks process also creates a checklist of your tasks for monitoring your progress as you complete your unique set of manual configuration tasks.
Task 4.7: Track Manual Tasks
Run option 5 Track Manual Tasks to display the checklist for your set of manual tasks. All persons involved in completing the tasks can display this list and use the C line command on the tasks to indicate when they are completed or validated as needing no action. The Performance Test installer can monitor the status of tasks being completed by everyone through this checklist.
This checklist is only for keeping track of progress and serves no other technical purpose. You may choose not to use this checklist if you track progress in another way.
Task 4.8: Perform PARMLIB Gen
Run option 6 Parmlib Gen. This will create a sample PARMLIB member for Performance Test using selections and values set during “Product Configuration” tasks. The member name is HSCM00, and it will be written to the .INSTALL library, overwriting the member if it already exists.
Related Topics