Introduction of Advanced Configuration Guide
This space supplements the .Installation and Configuration Guide providing further customization instructions and reference information.
Overview
This document is intended to guide you through any additional tasks involved in installing/updating, configuring, deploying, and troubleshooting Performance Test that are not covered in the .Installation and Configuration Guide.
Additional resources
Refer to these other sources of information on Performance Test.
Online documentation
The Performance Test product installation package does not include the product documentation. Access the Performance Test documentation from the BMC Support Center website at BMC Support Center in the following electronic formats:
- Release Notes in HTML format
- Product manuals in PDF format
- Product manuals in HTML format.
The product documentation is available for viewing or downloading:
- View PDF files with the free Adobe Reader, available at http://www.adobe.com.
- View HTML files with any standard web browser.
Customer solutions
Visit the BMC Support Center, to find product documentation, knowledge articles, and other technical resources. You can open a case with the Customer Solutions team, order products, and much more.
Contact Customer Solutions by phone:
- USA and Canada: 1-800-538-7822 or 1-313-227-5444.
All other countries: Contact your local BMC Software office. Contact information is available at BMC Support Center.
Visit BMC Software on the web at https://www.bmc.com for additional product information.
Information for customer solutions
If problems arise, please check your manual for assistance. If problems persist, please obtain the following information before calling BMC Software for assistance. This information will help determine the exact cause of the problem as quickly as possible.
- Identify the release number of BMC products in use.
- Identify the operating system.
- Identify the release of CICS Transaction Server that is being used.
- If an abend occurs, note the displacement and the module in which it occurs. If possible, obtain a copy of the system dump.
- Note the sequence of steps (including all commands issued) that resulted in the problem. Also note any variable data types and programming languages involved.
- To receive product fixes electronically, be ready to provide your email address.
Product delivery options
We have made the following product delivery options available:
- Receive From Network (RFN)
- Extended Play (EP) media on DVD or electronic FTP download.
Receive From Network (RFN)
The Receive From Network (RFN) process enables you to receive the product directly to your z/OS environment and install it using System Modification Program Extended (SMP/E).
After completing your product order from BMC’s online ordering system, you receive an e-mail message containing sample JCL to FTP the Installer which has been customized to include installation information of your current order. Your order e-mail also includes a copy of the BMC Installer Mainframe Products SMP/E Installation. The e-mail may also contain links for downloading any PC-based products that may have been ordered at the same time.
The BMC Installer is used to generate the JCL for SMP/E processing of your BMC mainframe products, including the Receive From Network step which FTPs the binary data from the FTP site directly to your z/OS Environment.
Post-installation product configuration should still be done according to the procedures in the .Installation and Configuration Guide supported by the information in this .Advanced Configuration Guide.
Extended Play (EP) Media
Performance Test can also be delivered as part of an installation media (DVD) or electronic FTP download.
Information on the Product Media Label
When Performance Test is delivered as part of the Performance Test installation media, some of the label information applies to installation capability, as noted below:
This DVD contains: List of the included Performance Test products identifying each product’s name and release number.
Security: Minimum level of BMC AMI's License Management System required.
Created on: The Performance Test installation media label shows when it was made. Compare this creation date with any maintenance posted on the BMC Support Center website at BMC Support Center.
If additional maintenance has become available since the date on the installation DVD, either download the maintenance from the BMC Support Center website, or contact Performance Test Customer Solutions (see Customer Solutions) to request new installation media with the current maintenance.
Available installation procedures
The SMP/E installation procedures vary depending on the Performance Test delivery option.
Installing with Receive From Network (RFN)
Follow the procedures as described in RFN SMP/E Installation of BMC AMI Mainframe Products of the BMC Installer Mainframe Products SMP/E Installation. After the successful SMP/E installation, continue with product configuration as described in the Configuring Performance Test — New Installation milestone or the milestone of the .Installation and Configuration Guide.
Installing from Performance Test EP Media with SMP/E Install using ISPF
Follow the procedures as described in SMP/E Installation Using the EP Media Interface of the BMC Installer Mainframe Products SMP/E Installation until you successfully complete the Upload Files step, then continue with SMP/E Installation Using the ISPF Interface.
After the successful SMP/E installation, continue with product configuration as described in the Milestone 3: Configure Performance Test — New Installation or Milestone 4: Configure Performance Test — Upgrade in the .Installation and Configuration Guide.
SMP/E installation
Follow the procedures as described in the BMC Installer Mainframe Products SMP/E Installation. After the successful SMP/E installation, continue with the product configuration as described in the Installation-and-Configuration-Guide.
SMP/E maintenance
We recommend that you periodically obtain and apply maintenance to keep your product version current. All maintenance for Performance Test and each of its releases is provided on the BMC Support Center website at BMC Support Center.
Locate the Downloads section for the Performance Test product and select the release for which you wish to apply maintenance. Follow the instructions on the website for acquiring the maintenance.
Optionally you may acquire maintenance by getting a current copy of the Performance Test EP media and using it to generate the JCL for applying maintenance via SMP/E.
To install the Performance Test maintenance to an existing installation, perform the steps described in Applying Maintenance.
Identify required personnel
This section provides information to help you determine the personnel necessary to perform your installation, configuration, and implementation.
MVS System Programmer
Your MVS system programmer may need to do the following:
- Install and add the Performance Test option to an ISPF menu. This step is required.
- Authorize the Performance Test load library. This step is required.
- Enable SSL for your web server. This step is required if you plan to capture SSL TCP/IP data.
MVS Operator
Your MVS operator may need to do the following:
- Start or stop the Global Recording Started Task in a given system or systems.
- Schedule starts and stops as required to meet site standards for availability, data set backups or restores, and so forth.
These tasks are described in Global-Recording-Administration.
VTAM System Programmer
Your VTAM system programmer may need to do the following:
- Add 3270 and LU0 APPLIDs to SYS1.VTAMLST. The 3270 and LU0 APPLIDs are required for each TSO user needing access to Performance Test.
- Add APPC APPLIDs to SYS1.VTAMLST. The APPC APPLIDs are required to use the APPC testing features.
- Assemble and link edit a logon-mode table into SYS1.VTAMLIB. A logon-mode table entry is required if you are not using the IBM default.
CICS System Programmer
If your users will be testing CICS LU6.2 transactions, have your CICS system programmer define APPC connections and sessions to CICS. For more information, see Setup Considerations.
Security Administrator
If you have an external security package installed, your Security Administrator may need to write rules controlling access to Performance Test data sets and functions. .Performance Test Security, contains information on how Performance Test interfaces with external security packages. Your Security Administrator may also need to set up:
- A Key Ring database for users performing SSL playbacks.
- An OMVS segment for each user performing TCP/IP or WebSphere MQ playbacks or generating HFS report files.
Storage Administrator
Your Storage Administrator may need to coordinate storage for Performance Test for VTAM data sets.
System Environment Requirements
Performance Test for VTAM System Environment
Virtual Storage
When working with 3270 scripts, the amount of storage that Performance Test for VTAM requires can vary. Depending on the options activated by the user, Performance Test for VTAM requires approximately 300 KB of virtual storage in the TSO region.
DASD Storage
Performance Test for VTAM requires approximately 3000 tracks for product installations on a 3390 device. In addition to the installation data sets, you can allocate repositories, script data sets, journal, log, and AutoDoc output data sets. Depending on your needs, these data sets vary in size. Performance Test for VTAM writes all user output data sets in VB format to minimize required DASD storage.
Unattended Mode Virtual Storage
Depending on the options you choose, Performance Test for VTAM requires approximately 250 KB of virtual storage for program storage and approximately 50 KB of virtual storage for each simulated terminal user.
Unattended Mode Caching Storage
Script caching reduces the number of I/Os for scripts run more than once, thereby controlling the file I/O used to access the scripts. You can use the following numbers as a guideline for estimating the amount of storage needed to run a playback.
Script Storage
Initial size: 1 MB. Increment size: 1 MB.
Script Storage Header
136 bytes (acquired storage above 16-MB line).
Member (Script Control Blocks)
Each control block is 160 bytes (acquired storage above 16-MB line).
- Initial size: (160 bytes x [no. of SCRIPT cards]) + 88-byte header
- Increment size: (160 bytes x [{no. of SCRIPT cards}/2]) + 88-byte header
Node (Port Control Blocks)
Each control block is 88 bytes (acquired storage above 16-MB line).
- Initial size: (88 bytes x [{no. of GROUP, ALLOCATE, or ACCEPT cards} x {no. of SCRIPT cards}]) + 88-byte header + 4100-byte hash table
- Increment size: (88 bytes x [{(no. of GROUP, ALLOCATE, or ACCEPT cards) x (no. of SCRIPT cards)}/2]) + 88-byte header
File (Data Control Blocks)
Each control block is 272 bytes with DF/SMS and 216 bytes without DF/SMS (acquired storage below 16-MB line).
- With DF/SMS:
- Initial size: (272 bytes x 10) + 88-byte header + 4100-byte hash table
- Increment size: (272 bytes x 5) + 88-byte header
- Without DF/SMS:
- Initial size: (216 bytes x 10) + 80-byte header + 4100-byte hash table
- Increment size: (216 bytes x 5) + 88-byte header
In addition, a buffer equal to the block size is acquired. The acquired storage is from above the line with DF/SMS, or below the line without DF/SMS. The hash table is acquired storage from above the 16-MB line.
DBCS Support
Performance Test for VTAM supports DBCS (Double Byte Character Set) used primarily to display Japanese Kanji characters during 3270 testing.
Script Dataset Allocation
Although Performance Test for VTAM no longer requires a preallocated script data set (recording file), some sites may still want to perform this function. If so, consider the following:
- The minimum LRECL should equal the length of the longest screen width plus (+) 18 additional bytes.
- The script data set is a standard partitioned data set (PDS) with variable blocked format.
- To allocate a data set before entering Performance Test for VTAM, use ISPF’s standard ALLOCATE NEW DATA SET screen, normally under ISPF option 3.2.
- The amount of space needed for the script files depends on the amount of data recorded. BMC recommends a block size of 9004.
Command-List Checking
If you are using a security package with command-list checking, add the following statements to the list for universal access:
Security Package and Command-List Checking Statement
If You Use | Then Add |
|---|---|
Domain Traveler | ETRMLDEF |
Unattended Processing | ETRMFEIT |
REXX Processor | SPINTRFC |
Date Change | SPINTRDC |
Date Find | SPINTRDF |
Input Field Formats | SPCURSOR |
Multichange Processor | SPCHGINT |
Security Script Processor | SPCPWSCK |
Euro Script Processor | SPCPWSCK |
GST | SPINTGST |
Message Filtering | SPMFINTF |
Statements you may need to include are:
ADDSD ‘COMPWARE.SQQFLOAD’ UACC(EXECUTE)
/*prevents users from copying programs*/
RDEFIN PROGRAM * ADDMEM(‘COMPWARE.SQQFLOAD’//NOPADCHK) UACC(NON)
/*makes all programs controlled*/
SETROPTS WHEN(PROGRAM) REFRESH /*puts the new PROGRAM profile into
storage*/
PERMIT * CLASS(PROGRAM) ID(user) ACCESS(read)
Refer to your security package’s documentation for additional information on command-list checking.
Performance Test for Mainframe Servers System Environment
Virtual Storage
When working with TCP/IP playback scripts, we recommend running in REGION=0M. When working with LU2 or APPC scripts, the amount of storage that Performance Test for Mainframe Servers requires can vary. Depending on the options activated by the user, Performance Test for Mainframe Servers requires approximately 300 KB of virtual storage in the TSO region.
DASD Storage
Performance Test requires approximately 2500 tracks for product installations on a 3390 device. In addition to the installation data sets, you can allocate repositories, script data sets, conversation logs, collection databases, and text, CSV, and HTML reports. Depending on your needs, these data sets vary in size. By default, Performance Test for Mainframe Servers uses VB format to conserve DASD storage; it also allows the following output data set record formats: F, FB, V, and VB.
Unattended Mode Virtual Storage
Depending on what options you choose, Performance Test requires approximately 250 KB of virtual storage for program storage and approximately 50 KB of virtual storage for each simulated terminal user.
Unattended Mode Caching Storage (APPC/3270)
Script caching reduces the number of I/Os for scripts run more than once, thereby controlling the file I/O used to access the scripts. You can use the following numbers as a guideline for estimating the amount of storage needed to run a playback.
Script Storage
Initial size: 1 MB. Increment size: 1 MB.
Script Storage Header
136 bytes (acquired storage above 16-MB line).
Member (Script Control Blocks)
Each control block is 160 bytes (acquired storage above 16-MB line).
- Initial size: (160 bytes x [no. of SCRIPT cards]) + 88-byte header
- Increment size: (160 bytes x [{no. of SCRIPT cards}/2]) + 88-byte header
Node (Port Control Blocks)
Each control block is 88 bytes (acquired storage above 16-MB line).
- Initial size: (88 bytes x [{no. of GROUP, ALLOCATE, or ACCEPT cards} x {no. of SCRIPT cards}]) + 88-byte header + 4100-byte hash table
- Increment size: (88 bytes x [{(no. of GROUP, ALLOCATE, or ACCEPT cards) x (no. of SCRIPT cards)}/2]) + 88-byte header
File (DCB Control Blocks)
Each control block is 272 bytes with DF/SMS and 216 bytes without DF/SMS (acquired storage below 16-MB line).
- With DF/SMS:
- Initial size: (272 bytes x 10) + 88-byte header + 4100-byte hash table
- Increment size: (272 bytes x 5) + 88-byte header
- Without DF/SMS:
- Initial size: (216 bytes x 10) + 80-byte header + 4100-byte hash table
- Increment size: (216 bytes x 5) + 88-byte header
In addition, a buffer equal to the block size is acquired. The acquired storage is from above the line with DF/SMS, or below the line without DF/SMS. The hash table is acquired storage from above the 16-MB line.
Performance Test for WebSphere MQ System Environment
Virtual Storage
When working with WebSphere MQ playback scripts, we recommend running in REGION=0M.
DASD Storage
In addition to the installation data sets, you can allocate repositories, script data sets, event summary reports, session logs, collection databases, and text, CSV, and HTML reports. Depending on your needs, these data sets vary in size. Performance Test for WebSphere MQ uses VB format by default to conserve DASD storage but allows output data set record formats of F, FB, V, and VB.
System Command Queue
If an application uses the system command queue, and Performance Test for WebSphere MQ will be sending PUTs to the system command queue, then the playback function of Performance Test for WebSphere MQ must have authorization to do this. See the appropriate IBM MQ documentation for more information.
PARMLIB overview
This section provides the information and procedures to configure and customize BMC mainframe products once the SMP/E installation of your products has completed. (See the BMC Installer Mainframe Products SMP/E Installation space for more information on installation of your BMC mainframe products.)
PARMLIB members
BMC mainframe products use parameter libraries, or PARMLIBs, to configure each product and common components. PARMLIB Member Parameters lists the Release 17.02 PARMLIB Members for all BMC mainframe products and common components. Your product requires a PARMLIB where its members are provided such that you can modify them to fit your site’s requirements.
We recommend using one common data set, but can be concatenation of data set names to store your site’s PARMLIB (if applicable) members in a common library. A copy of your product’s parameter files must reside in the //CWPARM DD concatenation of the BMC AMI Common Mainframe Services Controller (CMSC).
The BMC AMI Common Mainframe Services Controller (CMSC) address space is a centralized facility providing the common parameter library services. It provides two basic functions in relation to parameters: storage and retrieval. The following is a guideline for some of the usage and features of the CMSC:
- Users will modify a human readable PARMLIB member and issue a modify command to the CMSC to store this new set of parameters into a common memory object.
- This common memory object is accessible even if the CMSC is inactive.
- When the CMSC is initialized, all PARMLIB members are loaded into a common memory object.
- The default suffix is 00, but this can be changed in the CMSCnnnn PARMLIB member.
General guidelines for PARMLIB members
Parameters used by your BMC mainframe product or component are read from the PARMLIB data set. Edit the sample parameters to your site’s requirements.
General guidelines
PARM Name | Values | Samples |
|---|---|---|
Data columns | 1 to 71 | N/A |
Symbol separator | Underscore | "A_LONG_SYMBOL" |
Continuation | Check for “+” character in Column 72. | + |
Comments | “*” in column 1 | * is a comment |
- If the PARMLIB member includes multiple groups of parameters, for example for the definition of multiple Db2 Subsystem, then only one occurrence of each of the parameters within each group is allowed.
- Line level comments are supported using the “/*” to start a comment and “*/” to end the comment. Embedded comments are supported.
System symbolics
The CMSC resolves system symbolics as product parameters which are saved into storage, potentially allowing a single parameter member to be used across multiple LPARs. These symbols are defined by your installation in IEASYMxx. Issue the following display command to display the current symbols:
PARMLIB member naming convention
PPPPnnnn
PPPP is the product prefix (see General Guidelines).
nnnn is the 1 to 4-character PARMLIB suffix, for example 00.
The PARMLIB member name for each product or product component must start with the product prefix, for example FACM for File-AID Common Components. The 1- to 4-character suffixes can be used to replace the default name (FACM00). If the parameter for a given product is omitted, the default suffix will be 00.
Changing the default PARMLIB member
In the CMSC startup parameters, specify the product parameter, followed by the equal sign, and the 1- to 4-character suffix (for example: FACM=01, which points to PARMLIB member FACM01). If you changed your PARMLIB member name from the default FACM00 to FACM0005, for example, update your CMSC PARMLIB member to point to the new PARMLIB member, FACM=0005.
General guidelines for PARMLIB data set
- The data set can be blocked.
- The data set can have multiple extents.
- The data set must be on a single volume.
- The CMCS must have READ access.
PARMLIB member parameters
Product PARMLIB | Product |
|---|---|
AABD | Abend-AID BDCAS |
AADC | Abend-AID DCAS |
AAFA | Abend-AID Fault Analytics |
AATD | Abend-AID TDCAS |
AAVW | Abend-AID Viewer |
CMSC | Common Mainframe Service Controller |
FACM | File-AID Common Component |
FADA | File-AID/Data Solutions |
FADE | File-AID for Db2 Environment Information |
FAMV | File-AID/MVS |
FAFR | File-AID/RDX |
FAFD | File-AID for Db2 |
FAIE | File-AID for IMS Environment Information |
FAIX | File-AID for IMS |
HCI | Host Communications Interface |
HSCM | Performance Test |
LMCL | License Management Client (LMSINIT) |
LMSV | License Management Server (LMZINIT) |
STR | Strobe |
XCOV | Code Coverage |
XVGB | Code Debug CICS components |
XDGB | Code Debug CICS Global components |
XDDB | Code Debug CICS DBPA components |
XTSO | Code Debug TSO |
XCHG | Xchange |
PARMLIB product configuration
Step 1. Copy sample PARMLIB members
- Copy the provided sample PARMLIB members from your installation sample library to your site’s PARMLIB data sets.
Step 2. Update the CMSC with PARMLIB Information
- Make your product’s PARMLIB members available in the //CWPARM concatenation of the Common Mainframe Services Controller (CMSC). (See the Installing for further information on CMSC.)
- After making changes to your PARMLIB members, use the z/OS MODIFY command to update the CMSC with the changes you made to the PARMLIB member.
Refreshing all PARMLIB Members:
F cmscname,PARMLIB REFRESH
Refreshing a Single Parameter Member:
F cmscname,PARMLIB REFRESH member_name
For example, if you updated the parameters in member FACM00:
F cmscname,PARMLIB REFRESH FACM00