Configuring Performance Test
Guided configuration overview
Use the Guided Configuration program to configure and maintain your installation. The program presents the following options:
- Import Parm Settings — Imports values from an existing Guided Configuration database to save time during product migration/upgrade.
- Generate JCL Samples — Generate JCL samples for product usage.
- Product Configuration — Configures selected Performance Test products and features. You can also use this option to add or modify product features after configuration.
- Generate Manual Tasks — Generates manual task lists with customized instructions for tasks that must be performed outside of Performance Test installation, such as security system tasks. If you modify the installation, regenerate the manual task lists and perform any new instructions.
- Track Manual Tasks — Provides a mechanism for tracking manual task completion.
- PARMLIB Gen — Create PARMLIB sample using selections and values set during Product Configuration tasks.
- Apply Maintenance — Creates the SMP/E RECEIVE and APPLY jobs for product maintenance.
If you are installing on multiple systems that share DASD, one installation may suffice. However, if your systems host different types of traffic or different volumes of an applicable type of traffic, you may need separate installations for optimum performance. If so, run the Guided Configuration program on each applicable system, selecting only the products and features required for testing on that system.
Launching the Guided Configuration dialog
The following instructions explain how to prepare and launch the Guided Configuration dialog.
Review and submit sample job $10CPYQF created during the SMP/E installation of Performance Test to create a copy of the Performance Test SQQFSAMP library that was originally created during the execution of the BMC Installer. The copied data set is used for Performance Test configuration. The data set name can be any name that your site requires, but a low level-qualifier of INSTALL is recommended.
- 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. For example,
TSO EX '<hlq>.install.dsn($$$SETUP)' If you have not previously executed this member, you will be prompted for the SMP/E ISPF table data set name as shown in the following figure.
SMP/E Installation Data Import screen. ----------------------- SMP/E Installation Data Import ----------------------- .
. Command ===> Scroll ===> .
. .
. Performance Test FMID: .
. .
. Specify the dataset name, fully qualified .
. without quotes, identified on The BMC Installer .
. SMP/E JCL Customization ISPF panel where .
. the SMP/E ISPF Tables were created. .
. .
. This dataset contains details about the SMP/E environment .
. built by the BMC Installer during the SMP/E install process .
. process for Performance Test .
. .
. Press ENTER to automatically import this information into .
. the customization system, PF3 to skip import, .
. or CANCEL to exit the customization dialog. .
. .
. .
. SMP/E ISPF Table Dataset Name .- Type in the data set name and press Enter. This is the data set specified during the SMP/E installation process as described in the BMC Installer Mainframe Products SMP/E Installation. You can also find the name in member $$KCWRPT under the section The dialog ISPF tables are stored in dataset.
The following Product Suite Guided Configuration screen appears. Throughout the documentation, this screen is often referred to as the “main menu”.
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 Compuware Parmlib Gen Create parmlib sample using selections and values .
. set during "Product Configuration" tasks. .
. .
. 7 Apply Maintenance Receive and apply Performance Test sysmods .
To make a selection, type the option number on the Option line at the top of the screen and press Enter. The options are ordered according to the logical flow of installation and configuration procedures.
Importing settings (optional)
Save time during migration by importing product and feature selections, parameter values, MVS resource assignments, and custom sign-on security specifications from an existing Guided Configuration database. The Configure Products screens present the imported values as the initial default values. To import settings:
- On the Option line of the Guided Configuration main menu, type 1 and press Enter. The Import/Migrate Performance Test Install Settings screen appears with the cursor on the Command line.
- Type I (import) and press Tab. The cursor moves the Import DSN field.
- Enter the fully qualified name, without quotation marks, of the INSTALL data set from which the Guided Configuration settings will be imported and press Enter. An example is hlq.QQF170.INSTALL. After the import is complete, the Guided Configuration presents a short message in the upper right-hand corner of the screen.
- Complete the rest of the configuration as described in this section.
Configuring Performance Test product features
After the product is installed, it is time to configure it. Performance Test products are highly configurable. You can save time by installing only the product features that your users require.
The Guided Configuration displays a list of product features. Then, based on your product and feature selections, it displays the appropriate product configuration screens and fields. Although screen presentation varies, navigation through the screens is the same for each product.
Select products and features
From the Guided Configuration main menu, select Product Configuration. The Select Products & Features to Configure screen appears. The features that are available in multiple Performance Test products are marked with an asterisk. The Guided Configuration prompts you only once for the information necessary to configure these features.
Select Products & Features to Configure screen
. Command ===> .
. .
. Place a slash(/) next to the desired products and optional components. .
. Press ENTER to continue, PF1 for help, or CANCEL to exit. .
. * indicates multi product options .
. Performance Test for VTAM .
. REXX Common Program Interface Graphical User Interface .
. *LU0 terminal definitions SIEM data generation .
. *Customer Support Diagnostics *External Security Interface .
. .
. Performance Test for Mainframe Servers .
. TCP/IP support APPC support .
. LU2 terminal definitions *LU0 terminal definitions .
. *Message mapping macro - MAPD *External Security Interface .
. *Customer Support Diagnostics SIEM data generation .
. .
. Performance Test for WebSphere MQ .
. *Message mapping macro - MAPD *External Security Interface .
. *Customer Support Diagnostics SIEM data generation .
. .
Features
To avoid repetition, features available for multiple products are defined only once.
Performance Test for VTAM
3270 and LU0 application testing tool.
REXX Common Program Interface
An Interface that allows REXX EXECs to communicate with 3270 applications.
Graphical User Interface
An optional feature to create a communication pipeline that allows information to flow from the mainframe to the client and from the client to the mainframe.
*LU0 Terminal Definitions
Support for LU0 application testing.
*Customer Support Diagnostics
A utility that produces a list of all PTFs applied to your installation. If a user calls BMC Customer Solutions with a technical issue, Customer Solutions may request a copy of this information to aid with diagnosing the issue. This features is available in all Performance Test products.
SIEM Data Generation
3270 Application Audit data can be delivered directly to SIEM tools.
*External Security Interface
An interface to external security packages. Performance Test supports security packages that use the SAF interface including RACF, ACF2, and Top Secret. Use this feature to secure access to specific Performance Test functions.
Performance Test for Mainframe Servers
3270, LU0, APPC, and TCP/IP application testing tool.
TCP/IP Support
Support for testing TCP/IP applications including TCP, HTTP, HTTPS, ECI, CTG, IMS Connect, and Db2 Connect.
APPC Support
Support for testing APPC applications.
LU2 Terminal Definitions
Support for testing 3270 applications.
Message Mapping Macro - MAPD
Support for Performance Test edit macros.
Performance Test for WebSphere MQ
WebSphere MQ application testing tool.
SIEM Data Generation
MQ Session Monitor data can be delivered directly to SIEM tools.
Configure Products
The Configure Products screen appears next. If the description text that appears to the right of an option indicates that the product was not selected for configuration, the option is disabled. To make a selection, type the option number on the Option line and press Enter.
Configure Products screen
. Option ===> .
. .
. .
. 1 Performance Test Install tasks for Performance Test for VTAM .
. .
. 2 Mainframe Servers Install tasks for Performance Test for Mainframe Serv .
. .
. 3 WebSphere MQ Install tasks for Performance Test for WebSphere MQ .
. .
The chosen product’s configuration screen appears next (Configure Performance Test for VTAM screen shows the Performance Test for VTAM screen). It displays a list of tasks based on the features you selected. This screen also shows the status of each task: PENDING, IN-PROGRESS, or COMPLETED. Some tasks are required for each product but need to be completed only once. When accessing the second or third product’s screen, these tasks are marked with the status you applied to the task during the configuration of the first product.
Upon initial entry of this screen, the cursor appears on the Command line. To select all PENDING or IN-PROGRESS tasks, type ALL. Otherwise, press Tab to access the selection field for the first task. Type a forward slash (/) next to the tasks you need to complete. Press Enter to continue.
Configure Performance Test for VTAM screen
. Command ===> .
. .
. Performance Test for VTAM .
. .
. Place a slash(/) on each task line you wish to execute at this time, or .
. enter (A)ll on the command line to execute all PENDING and IN PROGRESS tasks. .
. Press ENTER to continue, PF1 for help, or END to exit. .
. .
. Status .
. .
. Set VTAM Global Recording operational parameters . . . . . PENDING .
. Create the Global Recording Request File . . . . . . . . . PENDING .
. Install the Global Recording started task . . . . . . . . PENDING .
. Install Archive Repository Registry started task . . . . . PENDING .
. Install the Auto-start script create started task . . . . PENDING .
. Define virtual terminals . . . . . . . . . . . . . . . . . PENDING .
. Set up VTAM reporting asset library . . . . . . . . . . . PENDING .
. Enable ISPF edit macros . . . . . . . . . . . . . . . . . PENDING .
. Set up web-based reporting . . . . . . . . . . . . . . . . PENDING .
. Install Search on Switch started task . . . . . . . . . . PENDING .
. Install Site Profile Dataset . . . . . . . . . . . . . . . PENDING .
. Set up ATV Manager . . . . . . . . . . . . . . . . . . . . PENDING .
. Set up Strobe for the ATV Manager . . . . . . . . . . . . PENDING .
. Install SMTP Email Services . . . . . . . . . . . . . . . PENDING .
. Establish access to the Product Suite . . . . . . . . . . PENDING .
The screen that corresponds to the first selected task appears. For field definitions, press the Help key or see Guided Configuration Field Definitions.
Read the instructional text at the top of the screen. In most cases, pressing Enter advances the Guided Configuration to the next screen. However, some screens require issuing primary commands before advancing to the next screen. On these screens, press End to continue.
To exit a screen without saving your work, type CANCEL, or CAN, on the Command line and press Enter. The Guided Configuration presents the screen that corresponds to the next selected task unless no more tasks are selected. If there are no more tasks, the Guided Configuration returns to the Configure product screen from which you started.
After each installation task screen, the Set Task Status prompt appears. Type 1 for Completed, 2 for In Progress, or 3 for Pending and press Enter.
Set the task status to record your progress and easily identify remaining tasks. For example, if more information is required to complete a particular task, mark it “In Progress”. Continue configuring the product. Return later, after having collected the requisite information to complete the Pending and In Progress tasks.
Set Task Status Prompt screen
. C .-----------------------------------------------------. .
. | SET TASK STATUS | .
. | | .
. | Select the appropriate status to display as the | .
. | current disposition of installation task: | .
. | Set VTAM Global Recording operational parameters | . . . . 4 .
. | | . . . . 128 .
. | Select Status: | . . . . 1000 .
. | 1 1. Completed | . . . . N .
. | 2. In Progress | . . . . Y .
. | 3. Pending | . . . . RACF .
. | | .
. | | .
. | | .
. '-----------------------------------------------------' .
The task screen for the next selected task appears. If no more tasks are selected, the Guided Configuration returns to the Configure product screen from which you started. To configure a second product, press End to return to the Configure Products screen and repeat these steps.
Modify features
Feature modifications may require using the Product Configuration dialog. For example, adding additional terminals requires using the Product Configuration option, while changing the Global Recording buffer settings can be done by editing and refreshing the PARMLIB member in the CMSC region.
To modify a currently installed feature with the Product Configuration option:
- From the Guided Configuration main menu, select Product Configuration. The Select Products & Features to Configure screen appears. It presents the selections made during initial installation. Leave the existing selections. Press Enter to continue to the next screen.
- The Configure Products screen is displayed next. On the Option line, enter the number for the product being modified. The chosen product’s configuration screen appears next showing all of the tasks with a status of COMPLETED.
- Type a forward slash next to the tasks that corresponds to the product features you need to modify. For example, if you need to modify your terminal definitions or add more terminals, select the Define Virtual Terminals option.
- The screen that corresponds to the first selected task appears. For field definitions, press the Help key or see Guided Configuration Field Definitions.
Read the instructional text at the top of the screen. Some screens require issuing primary commands before advancing to the next screen.
To exit a screen without saving your work, type CANCEL, or CAN, on the Command line and press Enter. The Guided Configuration presents the screen that corresponds to the next selected task unless no more tasks are selected, in which case, it returns to the Configure product screen from which you started. - After each task screen, the Set Task Status prompt appears. Type 1 for Completed, 2 for In Progress, or 3 for Pending and press Enter.
- The task screen for the next selected task appears. If no more tasks are selected, the Guided Configuration returns to the Configure product screen from which you started. To modify features in other products, press End to return to the Configure Products screen and repeat Step 2 through Step 6.
- Use the PARMLIB Gen option to create a new member using any updated configuration values. Compare this new member to the HSCM member currently in use to identify new parameter values set due to the modification. Either replace or edit the HSCM PARMLIB member to set the changed values and refresh the member in CMSC.
- Use the Generate Manual Tasks option as described in Manual Task Lists. Use the Track Manual Tasks option to track progress and ensure all manual tasks are completed.
Manual task lists
Some installation procedures vary depending on environment and site standards. Some tasks require specialized knowledge. Some require access to parts of the system that are highly secured. These tasks must be performed manually by personnel with the appropriate security clearance. The Guided Configuration generates customized instructions for these tasks based on the values supplied in the BMC Installer and Product Configuration options. It generates the following members into the install library from which the Guided Configuration was executed:
- TSKSECUR — Security system tasks
- TSKMVS — MVS tasks
- TSKVTAM — VTAM tasks
- TSKCICS — CICS tasks
- TSKIMS — IMS tasks.
Generate the manual task lists and, if necessary, distribute them to the appropriate personnel to be accomplished. Use the Track Manual Tasks option, discussed next, to track progress.
Whenever you modify the installation, regenerate the manual task lists and perform any new instructions.
To generate manual task lists, type 4 on the Option line of the main menu and press Enter. The Guided Configuration presents a message at the bottom of the screen indicating the names of the generated members and the library in which they are placed.
Tracking Manual Tasks
The Track Manual Tasks option presents a list of all of the manual tasks generated for your installation. The tasks initially are displayed with a status of “Pending”. Track progress by marking tasks “Completed”. Sort the list by task to see all of the tasks for each subsystem, or sort it by status to evaluate progress. Browse the task instructions for any task in the list.
To use the Track Manual Tasks option:
- On the Option line of the main menu, type 5 and press Enter.
- The Manual Task Checklist screen appears. The cursor is displayed on the Command line.
Use primary commands to change the order of the list, or to jump to the top or bottom of the list.
Press Tab to move the cursor to the selection line next to the first task. Use the up and down arrow keys to move the cursor though the list. Type the appropriate line command next to the selected task. The cursor automatically moves to the next task’s selection field. Issue one or more line commands and press Enter.
Press the Down key to scroll forward and the Up key to scroll backward. Scrolling the list causes the cursor to return to the Command line.
To exit the screen, press End.
Manual Task Checklist screen
. Command ===> .
. .
. Performance Test FMID: MQQF170 .
. .
. Press END when complete, UP to scroll backward, DOWN to scroll forward .
. PF1 for help, or CANCEL to exit. .
. .
. Line Command: (B)rowse task, (C)onfirm task completed, (P)Reset to pending .
. .
. CMD Status Task .
. --- --------- --------------------------------------------------------------- .
. Pending CICS: Install CICS terminal definitions .
. Pending IMS: Install IMS terminal definitions .
. Pending MVS: Add Peformance Test CLIST to ISPF panel .
. Pending MVS: Authorize Loadlib .
. Pending MVS: Review the Global Record Task JCL .
. Pending MVS: Install Support for Web-Based Reporting .
. Pending SECURITY: Command-List Checking .
. Pending SECURITY: Archive Record Registry Security .
. Pending SECURITY: Search On Switch Security .
. Pending SECURITY: Site Profile Dataset Security .
. Pending SECURITY: ATV Manager Security .
. Pending SECURITY: Repository Dataset Security .
. Pending SECURITY: Global Record Request File Access .
. Pending SECURITY: Autostart Script Creation Dataset Access .
On this screen, you can sort the list by status or task. The list is initially sorted by task. See the online help for details about using the SORT and other applicable primary commands.
The B (Browse) line command allows you to browse the manual task member in which the task resides. Use this option to review instructions. Press End to close the member. If more than one browse command was issued, the next selected member is displayed. Otherwise, the check list reappears.
The C (Confirm task completed) line command changes the status of the task to Completed.
The P (Reset to pending) line command changes the status of the task to Pending.
Generate PARMLIB Member HSCM00
Performance Testglobal product parameters are specified in a PARMLIB member. Two example parmlib members are supplied.
Performance Test
’s PARMLIB Sample Members
Library | Member Name | Contents |
|---|---|---|
Target library SQQFSAMP | HSCM00 | Sample Performance Test Parameter member with only core parameters that must be set for Performance Test to function. |
Target library SQQFSAMP | HSCMALL | Sample Performance Test PARMLIB parameter member with every product parameter and descriptions on coding values for them. |
Configuration library .INSTALL | HSCM00 | Initially this is a copy of member HSCM00 from the SQQFSAMP target library. After performing Task 3.7 for new installs or Task 4.7 for upgrades, it contains a sample PARMLIB member with values collected during import and configuration set as appropriate parameter values. |
A copy of the HSCM00 member must be updated and placed in the //CWPARM concatenation of the BMC AMI Common Mainframe Services Controller (CMSC) to make it available for product use.
The Guided Configuration dialog eases the task of customizing your PARMLIB member. After completing all of the tasks in the Product Configuration option, use the PARMLIB Gen option of the Guided Configuration facility. This will automatically tailor an HSCM PARMLIB member with values you specified during guided configuration. Member HSCM00 in the .INSTALL library will contain the result from the generation process. Review all parameter settings in this member to ensure they are set as desired, then copy the member to your CMSC PARMLIB. Use the CMSC MODIFY command to make the member available to Performance Test.
To make future parameter changes for Performance Test, simply edit the HSCM00 member in your CMSC PARMLIB, then activate the updated member with the CMSC MODIFY command.
To run the PARMLIB Gen, type 6 on the Option line of the main menu and press Enter. A Parmlib sample member HSCM00 generated message is displayed below the Command line.
Validating and repairing the installation
The Guided Configuration writes the install log, which tracks the history of the installation, as a mechanism for validating your installation and troubleshooting any issues.
The data set name for the install log is the same as the name of the data set containing the REXX EXEC used to launch the configuration dialog, except the last node is INSTLOG. For example, a REXX EXEC of '<userID>.QQF172.INSTALL' would result in an install log named '<userID>.QQF172.INSTLOG'. The install log reports all changes to the configuration database, as well as all changes to the target libraries.
To validate and repair the installation or to review the current state of your installation, see Installation Log.
Installation log
The Guided Configuration creates an install log that tracks the history of the installation. It reports every change made to the configuration database. Review the report to see the changes that the Guided Configuration made to your system or to see who modified the installation and when. This information can also aid BMC Customer Solutions with diagnosing issues.
Use ISPF to browse the installation log. Open the HISTORY member in the .INSTLOG library.
Applying maintenance
Periodically apply product maintenance to ensure that you are working with the most up-to-date version of the software.
To RECEIVE and APPLY Maintenance:
Download the latest cumulative maintenance file from BMC Support Center to request a new copy of the product with the current maintenance.
- On the Option line of the Product Suite Guided Configuration main menu, type 8 for Apply Maintenance and press Enter.
The Receive and Apply Product Maintenance screen appears. Fill in the fields and issue either the Edit command or the Submit command as follows:
- Use the E (Edit) command to generate the RECEIVE/APPLY JCL with the values supplied on this screen and present it in an ISPF Edit session. If you modify the JCL, submit it from the Edit Session.
- Use the S (Submit) command to generate the RECEIVE/APPLY JCL with the values supplied on this screen and submit the job.
Receive and Apply Product Maintenance screen
. -------------------- Receive and Apply Product Maintenance ------------------- .
. Command ===> .
. .
. Performance Test FMID: MQQF170 .
. .
. .
. Use (E)dit or (S)ubmit command to generate SMP/E JCL to receive and .
. apply product maintenance. Use PF1 for help, or END to exit. .
. .
. Note: The latest available cumulative maintenance file can be downloaded .
. from the BMC online technical support web BMC Support Central at: .
. https://www.bmc.com/support/support-central.html .
. .
. Maintenance file DSN .
. .
. Bypass Holdsystem (Y/N) .
. Apply CHECK . . . (Y/N) .- Specify the name of the data set containing the maintenance. This field is required.
- The Bypass Holdsystem sets the include-bypass-holdsystem flag. Enter Y to include the Bypass Holdsystem parameter on the SMP/E APPLY command statement. Enter N to exclude it.
- Apply CHECK sets the include-apply-check flag. Enter Y to include the Apply Check parameter on the SMP/E APPLY command statement. Enter N to exclude it.
Deploying the Performance Test Install
The Performance Test Install contains two sample batch jobs to assist in copying the Performance Test Install from the current LPAR location to satellite LPAR locations. The batch jobs are in the product Install Library used during the original Install and are to be used after the original Install has been completed.
The sample batch jobs are named QQFCOPY1 and QQFCOPY2. They utilize the Batch TSO Transmit function to send the identified data sets to the LPAR/UserID specified. QQFCOPY1 is dynamically built and uses the High Level Qualifier specified for the SMP/E Target libraries. QQFCOPY2 is a static sample that requires editing of the data sets before submission.
Both samples require editing of the Batch TSO Transmit command (XMIT) to identify the destination LPAR and TSO UserID that will receive the identified data sets. See IBM documentation TSO/E Primer for further explanation.
After the product install is complete, edit the sample jobs according to their Usage Notes. When submitted for execution, the jobs will package the specified data sets and transmit them to specified LPAR and TSO userID. The specified userID will have to log on to the specified LPAR and use the TSO RECEIVE Command to receive the data sets onto their new location. The TSO RECEIVE command allows for renaming the data sets, if that is desired.
The customizations needed to use the newly transmitted libraries include, but are not limited to the following:
- Performance TestPARMLIB Setting:
- All product file specifications, if they were renamed.
- The specifications needed for the ATV and Reporting.
- The Product Default Jobcard.
- The Global Record Request File specifications.
- Virtual Terminal Prefix and/or Suffix
- The specifications needed for the ATV.
- All elements installed on USS HFS/ZFS paths.
This is optional if Web-Based Reporting and Archiving were not installed. If either functionality is used, the elements needed would have to be verified on the new location. - All elements identified in the Manual Tasks list need to be validated for the new LPAR location.
- All elements installed into the original LPAR’s PROCLIB dataset need to be regenerated and validated.
- All Virtual Terminal elements installed on the original LPAR’s VTAMLST, CICS Regions, and/or IMS Regions need to be validated.
- All Security Rules need to be re-created and validated if the Security Package database (RACF/ACF2/Top Secret) is not shared across LPARs.