Introduction (MF User)

BMC Software is committed to providing user-friendly documentation in a variety of electronic formats. This section describes the available formats and how to access them, provides an overview of this manual and describes the conventions used within, and describes the resources available to help you.

Accessing Performance Test documentation

Performance Test documentation is available on the BMC Support Center website in HTML and PDF formats:

• Performance Test Release Notes — Provides recent information for the Performance Test product. In this file, you can quickly access technical notes and a list of the new features available in the release. The Release Notes may be updated throughout the life cycle of a release with the most current version located on the BMC Support Center for easy access to the latest product information.

• Performance Test  Installation and Configuration Guide — Provides installation and configuration procedures.
• Performance Test Advanced Configuration Guide — Supplements the Performance Test Installation and Configuration Guide, providing further customization instructions and reference information.
• Performance Test for VTAM User Guide — Explains how to use Performance Test for VTAM to test 3270 and LU0 applications.
• Performance Test for WebSphere MQ User Guide — Explains how to use Performance Test for WebSphere MQ to test WebSphere MQ applications.
• Performance Test for Mainframe Servers User Guide — Explains how to use Performance Test for Mainframe Servers to test APPC and TCP/IP applications.
• Performance Test Automated Testing Vehicle (ATV) Manager User Guide — Explains how to use the Performance Test ATV Manager to manage your testing environment and test cases.
• Performance Test Messages and Codes — Explains the messages and codes that Performance Test produces.
• Performance Test Scripting Reference — Introduces advanced script editing concepts and provides reference information for technical users.

View and print PDF files with Adobe Reader. Download a free copy of the latest version of the reader from Adobe’s web site: http://www.adobe.com.

HTML files

For your convenience, BMC Software also provides the Performance Test manuals in Hypertext Markup Language (HTML) format.

View HTML files with any standard Web browser. Simply click the HTML link on the selected BMC Support Center documentation page.

Access these formats on BMC Software’s Support Center website at BMC Support Center.

1. Log-in.
2. Select the desired product.
3. Click the Documentation link on the left selection bar.
4. Select the desired release. The BMC Support Center presents a documentation list containing links to each of the product’s manuals in all of the available formats.

Using this manual

This section describes the:

• contents of this manual
• notation conventions used throughout the manual
• command syntax and syntax diagrams.

Manual contents

This manual describes how to use Performance Test for Mainframe Servers. It contains the following subjects:

• Performance Test for Mainframe Servers Overview provides an overview of the product and testing process.
• APPC Global Recording and Scripts explains how to capture APPC traffic, monitor and modify recording requests, and generate testing scripts.
• APPC-Unattended-Processing-MF-User explains how to use Unattended Processing to generate unattended playback statements and JCL for batch testing APPC applications.
• Unattended-Playback-of-APPC-Scripts-MF-Userdescribes how to play back APPC scripts in batch including explanation of script tags, unattended mode statements, and sample JCL.
• APPC-Reporting-MF-User describes how to generate APPC reports using unattended processing statements and keywords, along with examples of the reports.
• TCP-IP-Global-Recording-MF-Userexplains how to create a recording request and how to monitor and maintain existing requests.
• TCP-IP-Scripts-and-Subset-Repositories-MF-User explains how to create scripts and subset repositories from a capture repository, how to edit scripts, and how to review and edit the TCP/IP message data.
• TCP-IP-Interactive-Playback-MF-Userdescribes how to play back your scripts interactively.
• TCP-IP-Unattended-Playback-MF-Userdescribes how to set up unattended playback of TCP/IP data, including script tags.
• TCP-IP-Reporting-MF-User explains how to create TCP/IP testing reports.
• Performance-Test-for-Mainframe-Servers-Profile-Defaults-MF-User provides information on how to edit your Performance Test for Mainframe Servers profile settings.
• TCP-IP-Data-Collection-and-Reporting-Tables-MF-User lists the TCP/IP fields that can be collected and reported.
• TCP-IP-Report-Field-Definitions-MF-User defines fields that appear in TCP/IP reports.
• TCP-Script-Create-Parameters-MF-User provides a list of the TCP script create parameters with a short description of the parameter.
• Customer-Support-Diagnostics-MF-User explains how to run a Customer Support Diagnostic Report that lists all PTFs applied to your installation.
• Glossary provides a description of terms used in this guide.

Notation conventions

This document uses the following notations to describe Performance Test screens and the information you enter on those screens:

• Technical revisions made to this document are indicated by revision bars in the left margin, as shown here.
• Sample screens generally show only the information appropriate to the accompanying text, for example:

• Blank lines or standard footings, as shown below, are usually omitted from screen illustrations.

• Information you enter is printed in boldface.
• Words defined within paragraphs are italicized.
• The phrase “select an option” refers to typing a slash next to one of the presented options and pressing Enter.

Command syntax

Performance Test uses statements and commands that you will learn about later. This section describes text conventions used in statement and command descriptions. It also explains how to read syntax diagrams.

• Keywords are shown in UPPERCASE letters. Enter keywords and special characters as shown. If a command or statement name can be abbreviated, the description shows only the abbreviation in uppercase letters.

The uppercase F in the command FIND means that you can enter the FIND command either as FIND or F.

• Variables and generic descriptions of parameter values are shown in lowercase letters.
• Vertical bars (|) are separators between mutually exclusive options.
• Brackets ([ ]) indicate optional parameters. All parameters not enclosed in brackets are required.
• Ellipses (…) indicate that the value can be repeated.

Reading syntax diagrams

Syntax diagrams define primary command syntax.

A parameter is either a keyword or a variable.

All KEYWORDs are shown in uppercase characters and must be spelled exactly as shown. You cannot substitute another value. If any part of a KEYWORD is shown in lowercase characters, that part is optional.

Variables are user-specified values and are printed in lowercase italics. For example, dataset-name indicates you are to substitute a value.

The syntax for commands is described in diagrams that help you visualize parameter use. The following example shows a command and a parameter:

Read the diagrams from left to right and from top to bottom. These symbols help you follow the path of the syntax:

Required parameters appear on the horizontal line (the main path). Optional parameters appear below the main path. Default parameters appear above the main path and are optional. The command executes the same regardless of whether the default parameter is included.

Vertically stacked parameters are mutually exclusive. If you must choose a parameter, one item of the stack appears on the main path. If the parameters are optional, the entire stack appears below the main path. If a parameter in a stack is the default, it appears above the main path.

If the same parameters are used with several commands, their syntax may be documented in a separate diagram. In the command syntax, these common parameters are indicated with separators before and after the parameter name.

An arrow returning to the left indicates a repeatable item. If the arrow contains a comma, separate the repeated items with a comma.

Accessibility

In accordance with section 508 of the Rehabilitation Act of 1973, BMC is committed to making its products and services easier to use for everyone including people with disabilities.

Performance Test is a mainframe application that runs on IBM’s z/OS operating systems. It has an ISPF interface that is accessed with IBM 327x-type terminals or with 3270 terminal emulator software. Since the mainframe environment offers few accessibility features, BMC has focused its attention, with regard to accessibility, on 3270 terminal emulator software running on personal computers (PCs) with Microsoft Windows 2000 or more current. Performance Test supports, with a few exceptions, Microsoft Windows accessibility features and Window-based Assistive Technology (AT) software and devices, such as Braille devices, screen readers, magnifiers, etc.

• Freedom Scientifics’ JAWS screen reader
• Attachmate Corporation’s myExtra Presentation Services tn3270 emulator
• Microsoft’s Windows accessibility features
• Adobe Reader using the “Read Out Loud” function.

This evaluation not only identified accessibility exceptions, but revealed emulator and screen reader compatibility issues that in some cases can be remedied through appropriate configuration.

Installing Windows accessibility features

Microsoft Windows operating systems offer several accessibility features to aid individuals who have difficulty typing or using a mouse, who are blind or have low vision, or who are deaf or are hard-of-hearing. Install these features during setup or later using the Windows installation disks. Refer to the “accessibility” topics in the Windows Help system for information on installing and using these features. Visit the Microsoft Web site, http://www.microsoft.com/enable, for additional information and tutorials.

Selecting font and font size

Microsoft Windows and emulator software packages offer font and font size settings to accommodate users with low vision. The emulator software’s tool bars and dialog boxes typically use the font specified in the operating system, while the terminal presentation uses the font and font size specified in the emulator. To change the font or font size:

• Presented on the toolbars and dialog boxes, refer to the Windows Help system.
• Presented in the terminal window, refer to the emulator’s documentation or Help.

Some screen readers recommend certain fonts and font sizes for compatibility. For example, Freedom Scientifics recommends setting the font to a common or “plain” font such as Lucida, Courier, or Times New Roman, and setting the font size to 10 points or smaller. Refer to the screen reader’s documentation or Help for these recommendations.

Changing color and contrast

Color and contrast settings can assist users with low vision. ISPF and most emulator software packages offer color and contrast settings. If you are accessing Performance Test with a terminal, use ISPF settings. Otherwise, adjust the color and contrast in the emulator software. Refer to ISPF Help or the emulator’s documentation or Help.

Setting cursor blink rate

The blink rate of the cursor can affect users with photosensitive epilepsy. Additionally, some screen readers require a specific blink rate. Some readers automatically adjust the blink rate while others expect you to adjust the rate. Refer to:

• The Microsoft Windows Help to find out how to set the cursor blink rate.
• The screen reader’s documentation or Help to find out the recommended blink rate.

Using keyboard shortcuts

Keyboard access to application functions support users who cannot use a mouse.

Microsoft Windows provides keyboard access to all functions within the operating system, such as:

• Displaying or hiding the Windows Start Menu
• Showing the Desktop
• Minimizing all windows
• Searching for files
• Accessing the help system
• Controlling the behavior of the Windows accessibility features, for example, toggling the listening status to the microphone, or cycling focus backward and forward.

Most Windows-based applications also provide keyboard access to their functions. The combination of keys required to execute a given function is called a keyboard shortcut. Refer to the “Keyboard Shortcuts” topics in the Windows Help system for a complete list of Windows shortcuts. For a list of the shortcuts that are available in the emulator software or any third-party accessibility tool, such as the JAWS screen reader, refer to the software’s documentation or Help.

Accessibility exceptions work arounds

During Performance Test accessibility evaluation, some exceptions were encountered where some accessibility features or AT were not fully supported. The causes of and solutions for these exceptions are currently under investigation by BMC Software.

Known exceptions

Accessibility exceptions include:

• Function Key (F Key) information at the bottom of the screen is not read by the screen reader on some screens. This is believed to be caused by an external interface. See Solutionsfor a viable work-around.
• Some system error and warning messages are not read by the screen reader when issued. Believed to be caused by an external interface. See Solutionsfor a viable work-around.
• Some pop-up dialog boxes or windows do not capture exclusive focus and are not read correctly by the screen reader. This is believed to be caused by an external interface. No known solution is currently available.
• System error and warning messages do not capture visual focus for the screen magnifier. This is believed to be caused by an external interface. No known solution is currently available.
• Some entry and display fields lack individual labels. When entry fields are accessed using the Tab key, the entire individual line is read.
• Current Web-based reports are not easily navigated using the keyboard and lack table element coordinate tags. Additionally, some of these reports contain color-coded elements — for example, the color of some elements conveys meaning.

Solutions

When the screen reader fails to read the F Key information upon entry to a new screen, do one of the following:

• Use the arrow keys to move the cursor down to the lines with the F Key information. The screen reader reads each line as the cursor is placed on it.
• Press the Page Up key for the screen reader to reread the entire screen.

When the screen reader fails to read an error or warning message, an audio alert occurs if this feature is enabled on your system. Press the Up key to place the cursor on the line containing the error message, usually on the top or title line. The screen reader reads the line and its error message individually.

Getting help

Visit the BMC Software Support Center, 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.

Visit BMC Software on the web at https://www.bmc.com for additional product information.