Installation and Customization Support Information

The information in this section supplements the Guided Configuration procedures in the Installation-and-Configuration-Guide. All customization should be done using the Guided Configuration facility.

Authorization of the Performance Test Load Library

The Performance Test load library must be authorized using one of the following methods:

Add the Performance Test load library to the APF list.
Copy the members of the Performance Test load library to an APF-authorized library.
Copy the members of the Performance Test load library to a link list library if your link list is authorized via the LNKAUTH parameter in member IEASYSnn of the SYS1.PARMLIB.

Access to Performance Test

Performance Test can utilize the LIBDEF utility to set up your ISPF environment. LIBDEF is not required to install Performance Test, but using it eases installation.

If your site:

uses LIBDEF, customize the CLIST as described in Installed with LIBDEF.
does not use LIBDEF, customize each TSO logon procedure as described in Installed without LIBDEF.

Installed with LIBDEF

Modify the LIBDEF member of INSTALL with the load, panel, message, exec, and table libraries (SQQFLOAD, SQQFPENU, SQQFMENU, SQQFEXEC, SQQFTLIB) created during Performance Test base installation.
Copy the LIBDEF member of INSTALL to a CLIST in the SYSPROC DD concatenation.
Add a path to Performance Test in the ISPF Primary Option Menu.

The PRIMARY member of INSTALL shows you how to modify the ISPF Primary Option Menu. Make sure you follow the format of the line labeled OPTION 2 (shown below) to start Performance Test with LIBDEF:

H,'CMD(%LIBDEF) NOCHECK' /*OPTION 2*/

Installed without LIBDEF

If your site does not employ LIBDEF, perform the following steps for each TSO logon procedure:

If the Performance Test SQQFLOAD library is not part of the system link list, add it to the ISPLLIB DD statement.
Warning
Important
For default library names, look in INSTALL member LIBDEF under HPERLLIB.
Concatenate the Performance Test panel library (SQQFPENU) to the ISPPLIB DD statement.
Concatenate the Performance Test table library (SQQFTLIB) to the ISPSLIB and ISPTLIB DD statements.
Concatenate the Performance Test SQQFEXEC library to the HPEREXEC DD statement.
Concatenate the Performance Test SQQFLOAD library to the HPERLOD1 DD statement.
Add Performance Test to the ISPF Primary Option Menu. See the PRIMARY member of the INSTALL library for an example of modifying the ISPF Primary Option Menu. In this member, the line labeled OPTION 1, shown below, indicates the correct format for starting Performance Test without LIBDEF:
H,'CMD(ETRMIMNU MAIN) NEWAPPL(EHPR)' /*OPTION1*/
Concatenate the Performance Test SQQFEXEC library to SYSPROC or SYSEXEC DD statement to enable the Performance Test REXX script processor.

Deploying Performance Test to additional LPARs

The Performance Test Install library 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:

HSCM PARMLIB member settings:
1. All product file specifications, if they were renamed.
2. The specifications needed for Performance Test/Eclipse, the ATV, and Reporting.
3. The Product Default Jobcard.
4. The Global Record Request File specifications.
5. Virtual Terminal Prefix and/or Suffix
6. 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 data set 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.

Performance Test shared features

Performance Test shared features include:

Global Recording to capture various types of activity on your system. Depending on your license, you can capture 3270, LU0, APPC, TCP/IP, and WebSphere MQ activity.

Important

Global Recording is a required component for

Performance Test

for WebSphere MQ and

Performance Test

for Mainframe Servers. It is optional for

Performance Test

for VTAM.

REXX Common Programmer Interface (CPI), which allows REXX EXECs to communicate with 3270 applications.
Web-Based Reporting to produce interactive HTML reports.
Customer Solutions Diagnostics to aid BMC’s Customer Solutions with diagnosing technical issues.

Additionally, Performance Test products share general and data set allocation parameters.

Global Recording

This section describes Performance Test’s Global Recording feature.

Setup considerations

This section provides Global Recording setup considerations.

Command-list checking

If your security package does not use command-list checking, skip to the next step.

If you are using a security package with command-list checking, add the Performance Test ETRMGRM0 statement to the list for universal access.

Statements you may need to include are:

SETROPTS WHEN (PROGRAM) /*activates program control*/
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)Review all statements carefully to make sure they fit your site-specific needs. For example, if resource program * already exists, RDEFINE may need to be changed to RALTER. Refer to your security package’s documentation for additional information on Command-List Checking.

Repository data set security

Performance Test’s Global Recording stores 3270, APPC, TCP/IP, and MQ data streams in repository data sets.

Restrict who can read from and write to these data sets because they can contain confidential data. Restrict access to these data sets to prevent unauthorized use.

If your installation controls access to end-user data sets, the Global Recording started task must have alter authority to create end-user repositories. See Performance Test Security for more information.

Data set security for HSSCREAT

The HSSCREAT procedure, applicable to Performance Test for VTAM and Performance Test for Mainframe Servers’ APPC testing features, must have update authority to update end-user script data sets and at least read authority to end-user repositories. The security administrator needs to enter the proper rules in your security package based on site installation standards, then inform end-users of these data set access rules. See Performance Test Security for more information.

To enable the message filtering feature of Global Recording:

Give the script create procedure HSSCREAT READ access to users’ REXX data sets, which contain the message filters.
Give the script create procedure HSSCREAT UPDATE access to users’ report data sets (such as session, conversation, and detail logs) that contain a record of all message filtering activity.

Reviewing the Global Recording request file

If you install the Global Recording function, periodically review the Global Recording request file to reduce overhead and improve processing efficiency.

Warning

If you plan to run

Performance Test

in multiple MVS systems with shared DASD, the Global Recording request file cannot be shared.

Global Recording request file

Create the Global Recording request file using the Guided Configuration as described in Configuring Performance Test.

Set parameter GLOBAL_RECORD_REQUEST_FILE in your HSCM PARMLIB to the name of the Global Recording request file you created during the Guided Configuration.
Ensure that the Global Recording started task and all users of Global Recording have UPDATE access to the request file.

Autostart script create procedure

When a Global Recording request ends, is FORCEd, or is STOPped, the autostart script create procedure begins if “Suspend Script Creation” is not selected on the 3270/LU0 - Capture Criteria screen or the APPC - Capture Criteria screen. INSTALL member HSSCREAT contains JCL used by the Performance Test subsystem.

Specify the correct data set names for the STEPLIB, HPEREXEC, and GRREQ DD statements.
Copy HSSCREAT to your system procedure library.

Important

If you want to prevent script create messages from appearing on your operator’s console, you can use the IBM z/OS message processing facility list function. The messages to be suppressed are listed in member MPFLST00 in data set SYS1.PARMLIB. The format to use is MESSAGEID,SUP(ALL). For more information, see the IBM manual z/OS MVS Initialization and Tuning Reference.

Global Recording startup parameters

EXTERNAL_SECURITY_PRODUCT – This parameter specifies your site’s external security package.
USERID_TRACKING – To activate user ID tracking, specify USERID_TRACKING=YES. This step is optional.

Warning
Important
If your site uses Top Secret, be sure to create and activate exit points for SVUSEREC. See Global Recording by User ID or for more information.
GLOBAL_RECORD_REQUEST_FILE – Specify the data set name of the Global Recording request file with parameter GLOBAL_RECORD_REQUEST_FILE in the HSCM PARMLIB member.
SCRIPT_CREATE_TASK – This parameter specifies the name of the autostart script create procedure. The default is HSSCREAT. A value of NONE disables autostart script create. The user initiates script generation any time after a capture repository is available.

There are additional parameters in the HSCM PARMLIB member that affect Global Recording and system performance. Their default values support testing in most moderate-volume systems. If you are testing in a high-volume or low-volume system, or if you are interested in optimizing performance, see Optimizing Global Recording Performance.

See Started Task Initialization Parameters for a discussion of all available initialization parameters.

Sample started task JCL

To customize the Global Recording started task JCL without using the Guided Customization dialog:

Copy GRTASK from the INSTALL library to your system procedure library.
On the STEPLIB DD statement, specify your load library.
(Optional) Modify the STATS DD statement if you want STATS information to be written to a DSN rather than the JES log.

Started task dispatching priority

Warning

Set the started task dispatching priority lower than VTAM, JESn, VLF, LLA, or other MVS-critical subsystems, but higher than any of your subsystems that generate VTAM, TCP/IP, or WebSphere MQ traffic, such as CICS, IMS, OMVS, or WebSphere MQ managers.

Global Recording batch interface

With the batch interface, users can:

Initiate and terminate recording from an operator’s console, a TSO session, or a PC using a test management tool.
Automate recording initiation/termination with a job scheduler.
Automate 3270, LU0, or APPC script creation. This feature applies only to Performance Test for VTAM and Performance Test for Mainframe Servers.

To enable the Global Recording batch interface:

Copy INSTALL member DCIPROC to your procedures library.
On the data set concatenations:
- Verify the name of the ISPF product data sets. Modify if necessary.
- Modify the Performance Test data set names according to your installation.
Modify the HPEREXEC DD statement to point to the Performance Test executable library at your installation.
Open INSTALL member DCIJCL. Modify the UPROCS statement to point to the procedures library containing DCIPROC.

Important

If you store the modified JCL in another library, notify your users. The instructions in the user guides indicate that this JCL is stored in INSTALL.

Repository encryption

Global Recording captures system activity, including sign-on transactions. It writes the recorded activity to data sets called capture repositories. The repositories can contain sensitive information such as user IDs and passwords or confidential client information. Prevent unauthorized access to the sensitive information contained in the repositories by securing the repository data sets with external security rules and by optionally enabling repository encryption.

Important

The script creation feature decrypts the activity to create scripts. Be sure to secure script data sets accordingly. See Performance Test Security.

To enable repository encryption, add the applicable encryption parameters to the HSCM PARMLIB member your site is using:

ENCRYPT_VTAM — Causes Global Recording and Archive Recording to encrypt VTAM data written to capture repositories.
ENCRYPT_TCP — Causes Global Recording to encrypt TCP/IP data written to capture repositories.
ENCRYPT_MQ — Causes Global Recording to encrypt WebSphere MQ data written to capture repositories.

Global Recording customization

Started task initialization parameters

Although the default settings may work, you can optimize both Global Recording and system performance by setting the parameters in the HSCM PARMLIB member to values appropriate for your system. Additionally, you can add or remove parameters to enable or disable certain functionality. This section describes all of the available initialization parameters. It also specifies the products and, if applicable, the technologies that each parameter affects.

Important

Selecting appropriate values for some of the initialization parameters requires knowledge of traffic volumes. Performance Test offers utilities that present volume and global capture buffer usage information. If you are unsure of the volume, or if the volume changes due to system modifications, use these utilities to help you determine the most appropriate values. Global Recording Administration details the utilities and includes instructions for optimizing Global Recording performance.

ECSA_BUFFER_COUNT

Description: Defines the number of VTAM recording buffers to allocate.

Set this three to four times the ratio of typical-to-peak volume. For example, if your typical volume is 150K/second and your peak volume is 450K/second (1:3), set this parameter between 9 and 12.

The default value of 4 supports most moderate-volume systems (100-200K per second with 200-1000 terminals).

Used with Performance Test for VTAM and Performance Test for Mainframe Servers: APPC.

Values: Number from 2 to 255.

Default: 4

ECSA_BUFFER_SIZE

Description: Defines the length of the global record capture buffers in K.

Set this equal to or half of the typical per second volume of VTAM traffic. For example, if your typical VTAM traffic is 150K/second, set this parameter between 75 and 150.

The default value of 128 supports most moderate-volume systems (100-200K per second with 200-1000 terminals).

Performance Test allocates this storage in a fixed subpool.

Used with Performance Test for VTAM and Performance Test for Mainframe Servers: APPC.

Values: Number from 32 to 1024.

Default: 128

MAXIMUM_TCP_CONNECTIONS

Description: Enter the expected number of TCP/IP connections.

Used with Performance Test for Mainframe Servers: TCP/IP.

Values: Number from 0 to 65535.

Default: 1000

ENCRYPT_VTAM

Description: Causes Global Recording and Archive Recording to encrypt all VTAM data written to repository data sets.

Used with Performance Test for VTAM and Performance Test for Mainframe Servers: APPC.

Values: YES or NO

Default: NO

ENCRYPT_TCP

Description: Causes Global Recording to encrypt all TCP/IP data written to repository data sets.

Used with Performance Test for Mainframe Servers: TCP/IP

Values: YES or NO

Default: NO

ENCRYPT_MQ

Description: Causes Global Recording to encrypt all WebSphere MQ data written to repository data sets.

Used with Performance Test for WebSphere MQ.

Values: YES or NO

Default: NO

MONITOR

Description: Specifying YES for this parameter activates the statistics monitor. Collects statistics when no capture requests exist. A value of YES bypasses performance features to enable throughput statistics.

Used with all products and technologies.

Values: YES or NO

Default: NO

MAXIMUM_MQ_CONNECTIONS

Description: Enter the maximum number of simultaneous WebSphere MQ queue manager connections plus the maximum number of objects (queues) that will be open simultaneously on the system.

Important

The QADR data structure is used internally by Performance Test to keep track of active MQ sessions in the MVS system. The initial number of QADRs obtained is controlled by the MAXIMUM_MQ_CONNECTIONS parameter. Error message TCPRC912I - MORE QARDS NEEDED appears if Performance Test has to keep track of more MQ sessions than are specified on the MAXIMUM_MQ_CONNECTIONS parameter.

You can eliminate this message by setting a MAXIMUM_MQ_CONNECTIONS value larger than the maximum number of simultaneous MQ sessions on your system. For each occurrence of this message, increase the existing MAXIMUM_MQ_CONNECTIONS value by at least 25%. For example, if the existing MAXIMUM_MQ_CONNECTIONS is 100 and you receive three of these messages, increase the MAXIMUM_MQ_CONNECTIONS to 175. Setting an appropriate MAXIMUM_MQ_CONNECTIONS value improves performance. A value that is set too low may use excessive CPU cycles.

Used with Performance Test for WebSphere MQ.

Values: Number from 0 to 65535.

Default: 100

MQ_QUEUE_MANAGER_NAME

Description: Activates the WebSphere MQ data capture code within Performance Test Global Recording. The “subsystem_id” value can be any MVS subsystem ID (4 characters) defined for use by a WebSphere MQ subsystem. The specified WebSphere MQ subsystem does not have to be running, however it does have to be defined in the MVS Subsystem Name table. After the started task is active, data can be captured from any WebSphere MQ subsystem.

Used with Performance Test for WebSphere MQ.

Values: 4 characters.

Default: None

Required: Yes

ENABLE_APPC

Description: A value of NO prevents Global Recording from processing any APPC traffic, thereby saving system resources (CPU time in the Global Recording address space). Specify a value of NO for this parameter if you do not intend to capture any APPC traffic.

Used with Performance Test for Mainframe Servers.

Values: YES or NO.

Default: YES

NFLS

Description: Specifying NFLS=NO ensures Global Recording flushes and processes global capture buffers as they fill with data. Use this option to capture activity in a system with a continuous volume of traffic, such as a production system. If you are capturing activity in a low-volume test system, consider using NFLS=YES.

Specifying NFLS=YES activates “early flush” logic in Global Recording. This causes Global Recording to flush and process the global capture buffers when a BIND or UNBIND occurs minimally 15 seconds after the last flush.

By default, Global Recording flushes and processes global capture buffers after they fill with data. If a captured session begins and ends before the buffer fills, the User count on the Global Recording Monitor Request screen and the Active Sessions screen will not reflect the existence of the session because the captured information has not been processed. If you are capturing data on a low-volume test system, specify NFLS=YES to flush and process the global capture buffers upon initiation and termination of captured sessions. This remedies the omission or delay of request monitoring information.

Do not specify NFLS=YES if you are capturing activity on a system with a continuous volume of traffic such as a production system. It could result in lost messages and greater CPU utilization.

Used with Performance Test for VTAM and Performance Test for Mainframe Servers: APPC.

Values: YES or NO

Default: NO

ENABLE_LU0

Description: A value of NO prevents Global Recording from processing any LU0 traffic, thereby saving system resources (CPU time in the Global Recording address space). Specify NO for this parameter if you do not intend to capture any LU0 traffic.

Used with Performance Test for VTAM.

Values: YES or NO

Default: YES

ENABLE_3270

Description: A value of NO prevents Global Recording from monitoring VTAM and from allocating buffers for VTAM monitoring, thereby saving system resources.

If you are installing only Performance Test for Mainframe Servers and do not need APPC support, specify YES for this parameter to improve system performance.

Used with Performance Test for VTAM and Performance Test for Mainframe Servers: APPC.

Values: YES or NO

Default: YES

OMVS_JOBNAME

Description: Specifies the jobname of the Open Edition address space.

Used with Performance Test for Mainframe Servers: TCP/IP.

Values: 1 to 8 characters.

Default: OMVS

REGISTRY_TASK

Description: Specifies the procedure used to create the archive registry entries.

Used with Performance Test for VTAM.

Values: 1 to 8 characters.

Default: HSRGSTRY

Required: Yes

MQ_SYNCPOINT

Description: A value of RELEVANT causes Global Recording to capture only relevant “syncpoint” events—that is, the MQ COMMITs or BACKOUTs associated with recorded GET, PUT, or SET events. Eliminating irrelevant “syncpoint” events from capture can result in smaller repositories and lower processing requirements for script creation.

Specify MQ_SYNCPOINT=ALL to capture all “syncpoint”. If you do not specify MQ_SYNCPOINT, Global Recording captures all “syncpoints”.

Used with Performance Test for WebSphere MQ.

Values: RELEVANT or ALL.

Default: ALL

SCRIPT_CREATE_TASK

Description: Specifies the procedure used to create scripts. If user specifies NONE, then no autostart script create is done.

Used with Performance Test for VTAM and Performance Test for Mainframe Servers: APPC.

Values: 1 to 8 characters.

Default: HSSCREAT

Required: Yes

EXTERNAL_SECURITY_PRODUCT

Description: Name of the security system installed on this MVS system. This parameter is required for both Global Recording and normal Performance Test security.

Values: RACF, ACF2, or TOPSEC.

Default: None

Required: Yes

MAXIMUM_3270_SESSIONS

Description: Maximum number of active VTAM LU-LU sessions expected at any one time on the MVS system where Global Recording runs. This value is typically in the 1000 to 20,000 range. As it increases, Global Recording uses larger amounts of ECSA (MVS common storage). The formula for the approximate amount of ECSA used by MAXIMUM_3270_SESSIONS is:

Bytes = 2500 + (MAXIMUM_3270_SESSIONS × 26)
For example, setting MAXIMUM_3270_SESSIONS=10000 uses approximately 262,500 bytes of ECSA.

Selecting a value close to the maximum number of VTAM sessions on your MVS system can minimize CPU use, eliminate unneeded data movement, and provide a higher probability of keeping up with your VTAM traffic.

If you issue the MVS DISPLAY NET,SESSIONS command, the resulting IST878I message tells you the current number of VTAM sessions on your system. Use the number of sessions displayed (at a peak volume time of day) as the MAXIMUM_3270_SESSIONS value.

Used with Performance Test for VTAM and Performance Test for Mainframe Servers: APPC.

Values: Number from 0 to 65535.

Default: 1000

TCP_SSL

Description: Specifies that SSL messages will be captured if set to YES. If NO is specified, SSL messages will not be captured.

Used with Performance Test for Mainframe Servers: TCP/IP.

Values: YES or NO.

Default: NO

STATS_FREQUENCY

Description: Alter the frequency of the statistics output. This also controls the CYCLE duration for statistics collection.

Used with all products/technologies.

Values: Number from 0 to 357913.

Default: 15

STATS_DSN

Description: OPENs the default STATDD or dynamically allocated data set specified by the STATS or STATS_DSN that collects statistics. The DEFAULT ddname of STATDD must be allocated to SYSOUT or a valid dsname with a data set RECFM of FBA and LRECL of 133 unless the DSN is entered with STATS or STATS_DSN. If a DSN is specified on the STATS_DSN or STATS, the STATDD will not be used and the dsname entered will be dynamically allocated. Global Recording must have update access to the DSN and the DSN must be cataloged before issuing the command.

Used with all products/technologies.

Values: 1 to 44 characters.

Default: None

STATS

Description: Activates collection of STATS output to the default STATDD or to a dynamically allocated data set as specified by the STATS or STATS_DSN when set to YES. STATS will always be collected for online display, but STATS also writes collected data to SYSOUT or other DSN. See STATS_DSNfor details on the DSN option and default ddname and DSN specifications.

Used with all products/technologies.

Values: YES or NO

Default: NO

SWITCH_REPOSITORY_TASK

Description: Name of the search on switch started task.

Used with Performance Test for VTAM, Performance Test for Mainframe Servers: TCP/IP, and Performance Test for WebSphere MQ.

Values: 1 to 8 characters.

Default: HSEARCH

Required: Yes

TCP_MQ_ECSA_BUFFER_SIZE

Description: Defines the global capture buffer length for TCP/IP and MQ capture.

Set equal to or half of the typical per second volume of TCP and MQ traffic. For example, if your typical TCP and MQ traffic combined is 150K/second, set this parameter between 75 and 150.

The HSCM PARMLIB member provides a default value of 128, which accommodates most moderate-volume systems (100K-200K/second).

Performance Test allocates these buffers in high virtual common storage fixed pages. If unable to allocate fixed storage, it will attempt to use pageable storage.

Used with Performance Test for Mainframe Servers: TCP/IP and Performance Test for WebSphere MQ.

Values: Number from 32 to 1024.

Default: 128

Required: Yes for TCP/IP or MQ capture.

TCP_MQ_ECSA_BUFFER_COUNT

Description: Defines the number of TCP/IP and MQ recording buffers to allocate.

Set 3 to 4 times the ratio of typical-to-peak volume. For example, if your typical TCP/IP and MQ combined volume is 150K/second and your peak volume is 450K/second (1:3), set between 9 and 12.

The HSCM PARMLIB member provides a default value of 4, which accommodates most moderate-volume systems (100K-200K/second).

Performance Test allocates these buffers in high virtual common storage fixed pages. If unable to allocate fixed storage, it will attempt to use pageable storage.

The actual number of buffers may be increased to fill an integral number of megabytes of storage.

Used with Performance Test for Mainframe Servers: TCP/IP and Performance Test for WebSphere MQ.

Values: Number from 2 to 255.

Default: 4

Required: Yes for TCP/IP or MQ capture.

TCPIP_JOBNAMES

Description: Specifies the jobnames of the TCP/IP address spaces that are eligible for capturing data. This parameter is required or TCP/IP will not be supported.

Used with Performance Test for Mainframe Servers: TCP/IP.

Values: Up to 8 jobnames, each from 1 to 8 characters, separated by a comma.

Required: Yes.

MAXIMUM_CONCURRENT_TCP_MQ_CALLS

Description: Maximum number of in-progress TCP/IP and MQ calls that Global Recording can track simultaneously.

Increasing MAXIMUM_CONCURRENT_TCP_MQ_CALLS causes Global Recording to allocate additional ECSA. Use the following equation to approximate the number of ECSA bytes used based on the value of this parameter:

Bytes= 2152 × MAXIMUM_CONCURRENT_TCP_MQ_CALLS
Used with Performance Test for Mainframe Servers: TCP/IP and Performance Test for WebSphere MQ.

Important

Setting MAXIMUM_CONCURRENT_TCP_MQ_CALLS too low may prevent Performance Test from recording all TCP/IP or MQ messages when traffic volume is high.

Values: Number from 0 to 65535.

Default: 100

MAXIMUM_TCP_RECORD_SIZE

Description: Maximum TCP/IP record size to record. Performance Test ignores any TCP/IP data record larger than this value. 0 indicates no limit. However, if set to 0 and a large record exceeds the total buffer space, Performance Test will run out of buffer space and begin issuing TCPRC100W error messages indicating that data is being lost.

Used with Performance Test for Mainframe Servers: TCP/IP.

Values: Number 0 or greater.

Default: Total buffer size (TCP_MQ_ECSA_BUFFER_COUNT multiplied by TCP_MQ_ECSA_BUFFER_SIZE).

Started task subsystem name

When the Global Recording started task first starts, it adds a 4-byte subsystem name that is defined in the SQQFMOD library member SVSSCTID. It reuses the subsystem name on subsequent starts. The default subsystem name is C'SVW.', where '.' is hexadecimal 12. In other words, the system name in hexadecimal format is X'E2E5E612'. Most sites operate with the default. However, if you want to modify the subsystem name, see Changing the Started Task Subsystem Name.

Automated Testing Vehicle (ATV) Manager configuration

The ATV Manager is a system for building, running and maintaining Automated Testing Vehicles (ATVs). The following steps will enable you to configure the ATV Manager. To create a new ATV Master Index file, use either the index file created at installation as a model, or use JCL member HSATVJCL in your INSTALL data set.

Edit HSATVJCL in your INSTALL data set by entering the ATV Master Index data set name and then execute HSATVJCL. Update the HSCM PARMLIB member parameter with the ATV Master Index data set name. This denotes the file that is used as an index for ATVs that are created.
Enter the ATV High Level Qualifier parameter (ATV_HIGH_LEVEL_QUALIFIER). ATV_HIGH_LEVEL_QUALIFIER is used as the High Level Qualifier, followed by the Vehicle name, for data sets created by the ATV Manager. Users will need ALTER access for these data sets in order to use the ATV Manager.
Set up your ATV Manager profile settings. For complete details on setting up your ATV Manager profile settings, see Option 11 – ATV Manager.
The ATV Master Index is a KSDS file and is used as an index for ATVs that are created. All user of the ATV Manager will need READ access to this data set. Users creating Vehicles will need CONTROL access.

Performance Test User Profile configuration

Profiles make it possible for the installer to set default options in user profiles at installation time. Performance Test uses profiles to help end-users tailor their view of the product.

The site profile data set attributes include:

Primary quantity - user defined
Secondary quantity - user defined
Directory blocks - user defined
Record format - VB
Record length - 256
Block size - 2564
Dataset name type - PDS

Important

Do not modify the original @@@@DFLT member in the site profile data set.

Function Package Directory for REXX CPI

Performance Test’s REXX Common Program Interface (CPI) allows you to access Performance Test using REXX. There are two ways to set up a Function Package Directory for REXX CPI. This is an optional installation step.

The CPI operates as a REXX function package (HSCPI) and must be contained in a function package directory.

IBM provides two dummy function package directory names, IRXFLOC and IRXFUSER. You can use either of these directories for the REXX CPI if either they are not currently used at your site, or if their usage can be isolated via a STEPLIB or JOBLIB library.

Make the function package load module accessible using either a STEPLIB or JOBLIB library, or by being installed in LINKLST or LPALIB.

INSTALL member CPIFPACK contains sample JCL to assemble the HSCPI into the IRXFLOC directory and place this load module in the Performance Test load library. Alternatively, you can change all IRXFLOC references to IRXFUSER. This creates IRXFUSER as the directory.

If you need to merge the HSCPI function package into an existing function package directory, review the TSO Extensions Version 2 REXX Reference Manual.

You can also use the ERXCPI module to set up REXX CPI. Use the ERXCPI module from the Performance Test load library.

In the REXX EXEC that uses the Performance Test CPI, change the HSCPI instructions. Change the function calls to HSCPI to call ERXCPI instead. For example, change:

x=hscpi('logon','SESID',y)

to:

x=erxcpi('logon','SESID',y)

When a REXX EXEC contains a function call (in this case, the function is called ERXCPI), REXX goes through a search order to find that function’s code. This search order is fully documented in the TSO Extensions Version 2 REXX Reference Manual. One of the search order steps is the load libraries. REXX will search for a function in the load libraries using the following search sequence:

Job pack area
ISPF ISPLLIB
Task library
Step library (STEPLIB)
Link pack area (LPA)
Link library.

If the Performance Test load library is allocated to one of the libraries (such as the STEPLIB in the user’s TSO session), it would be found in the REXX search order. That means when the ERXCPI function is attempted, REXX will find the ERXCPI module in the Performance Test loadlib, and the function will be properly run.

Support for web-based reporting

To install support for Web-based reporting:

In the HTTP Server configuration file (httpd.conf), add the following statements for HTTP Server powered by Domino:
Exec /QACenter-zOS/cgi-bin/* /u/Hiperstation/cgi-bin/*
Pass /QACenter-zOS/* /u/Hiperstation/*
or for HTTP Server powered by Apache:
ScriptAlias /QACenter-zOS/cgi-bin/ "/u/Hiperstation/cgi-bin/"
Alias /QACenter-zOS/ "/u/Hiperstation/"
Replace /u/Hiperstation/ with the path name supplied on the installation job generator ($$01JCLG) WEBDIR parameter. Make sure the first path following the statement is exactly as shown. These aliases are required for successful report generation.
Warning
Important
To ensure the HTTP server is configured to handle the reports created by Performance Test make sure the HTTP server configuration file (httpd.conf) contains the appropriate ADDTYPE entries for the following file types for HTTP Server powered by Domino:
AddType .htm text/html ebcdic 1.0 # HTML on PCs
AddType .html text/html ebcdic 1.0 # HTML
AddType .js text/plain ebcdic 1.0 # JavaScript
AddType .xml text/xml ebcdic 1.0 # XML
AddType .xsl text/xsl ebcdic 1.0 # W3C XSL
AddType .gif image/gif binary 1.0 # GIF
AddType .jpg image/jpeg binary 1.0 # JPEGor for HTTP Server powered by Apache:
AddType text/html .htm
AddType text/html .html
AddType text/plain .js
AddType text/xml .xml
AddType text/xsl .xsl
AddType image/gif .gif
AddType image/jpeg .jpg
Warning
Important
- The Performance Test for VTAM (QAH) installer must ensure that the PRODUCT_UNIX_PATH is accessible from a web browser. Although this can be achieved in several ways, the following is an example using the PASS or ALIAS statement in the HTTP server configuration file (httpd.conf) of the HTTP Server. For HTTP Server powered by Domino:
Pass /u/* /u/*
or for HTTP Server powered by Apache:
Alias /u/ "/u/"
- Report HTML, XML, and XSL files are written in EBCDIC. To ensure proper translation for HTTP Server powered by Apache, you may need to add CharsetOptions DGWCompat to the <Location />. entry in httpd.conf.
Open HSCM PARMLIB member in an ISPF Edit session. Supply the name of your HTTP server on the HTTP_SERVER_NAME parameter. This is the same value that is specified on the HOSTNAME entry found in the HTTP server configuration file (httpd.conf) or is returned in the server output log by the gethostname function that is called at HTTP Server startup when the HOSTNAME entry is not specified.
To further secure your Archive Search reports, you can add security to the HTTP server to prevent unauthorized users from accessing your Archive Search Report directory by using a either PROTECT entry for HTTP Server powered by Domino or a location entry for HTTP Server powered by Apache to force RACF authorization whenever the URL for an Archive Search report directory is accessed. To do this for HTTP Server powered by Domino, make sure the HTTP server configuration file (httpd.conf) contains the appropriate PROTECTION and PROTECT entries for the main Performance Test Archive HFS directory:

Protection PROT-ARCHIVE {
ServerId your-sysid
AuthType Basic
PasswdFile %%SAF%%
UserId %%CLIENT%%
GetMask ALL
}

Protect /u/QACenter-zOS/archive/* PROT-ARCHIVE

To do this for HTTP Server powered by Apache:

<Location ~ "/QACenter-zOS">
AuthName "Hiperstation_SAF"
AuthType Basic
AuthBasicProvider saf
Require valid-user
SAFRunAS %%CLIENT%%
</Location>

Important

Make sure that the line

{{code language="none"}}
LoadModule authnz_saf_module modules/mod_authnz_saf.so
{{/code}} is in httpd.conf for HTTP Server powered by Apache and not commented. It should be before <Location> tag above.

By default, Performance Test defines individual Archive Search report directories with the end-user’s TSO user ID as the HFS directory owner. Do not change this if you want to prevent other people from accessing those end-user directories.

Enabling the Customer Solutions Diagnostic

Performance Test provides 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.

To enable the Customer Solutions Diagnostic for your users:

Grant users READ access to the SMP/E data sets.
Within the HSCM PARMLIB member, modify the values of the following variables:
1. GLOBAL_CSI: Specify the name of the Global CSI data set.
2. TARGET_ZONE: Specify the SMP/E Target Zone.

Also, ensure that the PRODUCT_REXX_EXEC variable points to your SYSEXEC load library.

General parameter defaults

The PARMLIB sample member HSCM00 contains the general parameter default values listed in this section. Review each parameter’s default value to ensure it supports your environment. If you modify any of these parameters, refresh your HSCM PARMLIB member.

APPC_LOGMODE

Description: Defines the 1- to 8-byte character name for the APPC log mode if one was not given in the unattended playback ALLOCATE or ACCEPT statement. The value must be enclosed in quotes if there are any non-alphanumeric characters.

Values: 1 to 8 bytes.

Default: #INTER

APPLICATION_PROFILING

Description: Sets the default value for the Use Application Profiling field in the Performance Test for VTAM Domain Traveler feature. Application profiling synchronizes script playback with application responses to ensure successful and efficient playback. It collects response time information to determine how long to wait for the next response. If the application does not respond in the expected time, Performance Test for VTAM automatically increases the wait up to the specified Maximum Wait. As Performance Test for VTAM gathers more data, wait times typically decrease.

Values: YES or NO.

Default: NO

AUTO_XMASK

Description: Automatically runs the XMASK playback at the end of every played script, so the masks in the mask buffer are used only for the current script.

Values: YES or NO.

Default: NO

DARK_FIELD_ACTION

Description: Determines the treatment of input data recorded in a script for non-display fields.

The value determines if the field data is encrypted or replaced by a “clear” character. Choose one of the following characters as a value:

DATA — field data present and encrypted for both online and Global Recording functions.
ALWAYSCLEAR, GLOBALRECORD, or TSO — replace field data with data set in the second value:
- ALWAYSCLEAR — always clear field data.
- GLOBAL_RECORD — clear field data for the Global Recording function only.
- TSO — clear field data for the TSO online component only.

Values: DATA, ALWAYSCLEAR, GLOBALRECORD, or TSO.

Default: DATA

DARK_FIELD_REPLACE

Description: This value is a two-character value representing the hexadecimal value of the character replacing each character of the field data. If DARK_FIELD_ACTION=ALWAYSCLEAR and this field are omitted, Performance Test replaces field data positions with the null character hex 00.

To choose blanks as the clear character, enter 40 for the value (for example, (C,'40')). If you choose DARK_FIELD_ACTION=DATA, omit this parameter.

Values: 2 characters.

Default: None

Required: No.

DEFAULT_USER_PROFILE

Description: The default user profile member in the site profile data set.

Values: 1 to 8 characters.

Default: @@@@DFLT

DOMAIN_TRAVELER_PROTECTED_FIELD

Description: Set this parameter to LIGHTPEN to check for light pen protected fields in 3270 LU2 type input data. Set this parameter to ALLPROT to ensure that protected fields do not create input fields.

Values: LIGHTPEN or ALLPROT

Default: LIGHTPEN

DOMAIN_TRAVELER_SECURITY_ENTITY

Description: Sets the second-level (type) qualifier that Performance Test uses with the RACF/SAF interface when validating the user’s authority to connect to a domain destination in Domain Traveler and 3270 Unattended Playback.

Values: TP or DD.

Default: TP

DOMAIN_TRAVELER_STATIC_LU

Description: Set this parameter to NO if you do not want Domain Traveler to try attaching to statically defined LUs. Statically defined LU names are defined as the character “e” plus the TSO logon ID. Set this parameter to NO only if you are certain you do not want Domain Traveler to attempt attachment to these LUs.

Values: YES or NO.

Default: YES

FIELD_TRAILER

Description: Determines how trailing blanks are removed from fields when inputs are sent to the domain destination.

When set to STATIC, the value of STRIP_TRAILING_BLANKS_NONZOOM is used for all fields sent to the domain destination (see STRIP_TRAILING_BLANKS_NONZOOM).

When set to FIELDCTL, trailing blanks are removed from fields defined as numeric (having an attribute of UNPROT,NUM) and fields where the last position is a null. Trailing blanks are preserved on all other fields. The value of STRIP_TRAILING_BLANKS_NONZOOM determines how inputs should be recorded to scripts.

Values: STATIC or FIELDCTL

Default: STATIC

GLOBAL_CSI

Description: The name of the Global CSI Dataset for this installation.

Values: 1 to 44 characters.

Default: COMPWARE.GLOBAL.CSI

Required: Yes.

GLOBAL_RECORD_CAPTURE_LU1

Description: Set this parameter to NO to ensure no Global Recording of 3270 LU1 type data occurs. Set this parameter to YES to globally record 3270 LU1 type data. LU1 type data is usually print data going to the master printer.

Values: YES or NO.

Default: NO

GLOBAL_RECORD_LU2_SECURITY

Description: Performance Test for VTAM can validate a user’s authority to update script and repository data sets when the user creates, updates, or restarts a Global Recording request. This parameter defines the types of data sets subject to this validation.

Set this parameter to:

ALL to have Performance Test for VTAM ensure the user has authority to update all data sets specified in the 3270/LU0 Global Recording Request.
SCRIPT to have Performance Test for VTAM ensure the user has authority to update the script data set specified in the 3270/LU0 Global Recording Request.
REPOS to have Performance Test for VTAM ensure the user has authority to update the repository data set specified in the 3270/LU0 Global Recording Request.
NONE if you do not need Performance Test for VTAM to validate update authority.

Values: ALL, SCRIPT, REPOS, or NONE.

Default: NONE

GLOBAL_RECORD_REQUEST_FILE

Description: Name of the Global Recording request file.

Values: 1 to 44 characters.

Default: COMPWARE.QQFnnn.GRREQ

Required: Yes.

GLOBAL_RECORD_LU6_SECURITY

Description: Performance Test for Mainframe Servers can validate a user’s authority to update script and repository data sets when the user creates, updates, or restarts an APPC Global Recording request. This parameter defines the types of data sets subject to this validation.

Set this parameter to:

ALL to have Performance Test for Mainframe Servers ensure the user has authority to update all data sets specified in the APPC Global Recording Request.
SCRIPT to have Performance Test for Mainframe Servers ensure the user has authority to update the script data set specified in the APPC Global Recording Request.
REPOS to have Performance Test for Mainframe Servers ensure the user has authority to update the repository data set specified in the APPC Global Recording Request.
NONE if you do not need Performance Test for Mainframe Servers to validate update authority.

Values: ALL, SCRIPT, REPOS, or NONE.

Default: NONE

GLOBAL_RECORD_MQ_SECURITY

Description: Performance Test for WebSphere MQ can validate a user’s authority to update script and repository data sets when the user creates, updates, or restarts a Global Recording request. This parameter defines the types of data sets subject to this validation.

Set this parameter to:

ALL to have Performance Test for WebSphere MQ ensure the user has authority to update all data sets specified in the Global Recording Request.
REPOS to have Performance Test for WebSphere MQ ensure the user has authority to update the repository data set specified in the Global Recording Request.
NONE if you do not need Performance Test for WebSphere MQ to validate update authority.

Values: ALL, REPOS, or NONE.

Default: NONE

GLOBAL_RECORD_TCP_SECURITY

Description: Performance Test for Mainframe Servers can validate a user’s update authority for script and repository data sets when the user creates, updates, or restarts a TCP/IP Global Recording request. This parameter defines the types of data sets subject to this validation.

Set this parameter to:

ALL to have Performance Test for Mainframe Servers ensure the user has authority to update all data sets specified in the TCP/IP Global Recording Request.
REPOS to have Performance Test for Mainframe Servers ensure the user has authority to update the repository data set specified in the TCP/IP Global Recording Request.
NONE if you do not need Performance Test for Mainframe Servers to validate update authority.

Values: ALL, SCRIPT, REPOS, or NONE.

Default: NONE

PRODUCT_LOADLIB

Description: The Performance Test load library data set name.

Values: 1 to 44 characters.

Default: COMPWARE.QQFnnn.SQQFLOAD

Required: Yes.

PRODUCT_PANELS

Description: The Performance Test panel library data set name.

Values: 1 to 44 characters.

Default: COMPWARE.QQFnnn.SQQFPENU

HIPERSTATION_PLAYBACK_CONTROL

Description: The Performance Test playback control library data set name. It is used to support the generation of the log file used to run playback and reporting jobs.

Values: 1 to 44 characters.

Default: COMPWARE.QQFnnn.CONTROL

PRODUCT_PROFILE

Description: The site user profile data set name.

Values: 1 to 44 characters.

Default: COMPWARE.QQFnnn.SITE.FILE

Required: Yes.

HIPERSTATION_REPORT_CONTROL

Description: The Performance Test playback control reporting control library data set name. It is used to support the generation of the log file used to run playback and reporting jobs.

Values: 1 to 44 characters.

Default: COMPWARE.QQFnnn.HS.REPORT

PRODUCT_REXX_EXEC

Description: Name of the Performance Test REXX data set.

Values: 1 to 44 characters.

Default: COMPWARE.QQFnnn.SQQFEXEC

Required: Yes.

PRODUCT_SAMPLES

Description: Name of the Performance Test samples data set.

Values: 1 to 44 characters.

Default: COMPWARE.QQFnnn.SQQFSAMP

HIPERSTATION_SAMPLE_SCRIPTS

Description: Name of the sample script data set which contains script examples.

Values: 1 to 44 characters.

Default: COMPWARE.QQFnnn.SQQFSCRP

JES2_NODE_NAME

Description: The job class that applications need to write to when sending e-mail.

Values: One character.

Default: B

Required: Yes.

JOURNAL_SECOND_OUTPUT

Description: Applies to creating journals when playing back a script.

Set this parameter to YES to create a journal entry for every output entry in the script. Set this parameter to NO if you do not want to create journal entries after a <SECOND> record is read until the next script input is read.

Values: YES or NO.

Default: YES

PRIMARY_OPTION_MENU_LANGUAGE

Description: Defines what language to use when displaying the Primary Option Menu. This parameter is used as a suffix to the module ETRM@xxx. For more information, see Performance Test for VTAM Primary Option Menu.

Values: 1 to 3 characters.

Default: ENU

NO_EXPIRY_CLASS

Description: Designed to be an SMS management class for non-expiring data sets (for example, those data sets that should never be automatically deleted because of age). These “live forever” data sets would typically be defined with JCL DD parameters such as RETPD=9999 (Retention Period) or EXPDT=1999/999 (Expiry Date).

The NO_EXPIRY_CLASS value is used in the definition of the “zero” or .#0000000 data set in an archive definition. The .#0000000 (seven zeros) is used to hold queued archive search requests and so should exist as long as the archive does, only being deleted when the user deletes the archive request via Global Recording. Thus, the use of the non-expiring management class is used to ensure it can never be deleted due to age.

Values: 1 to 8 characters.

Default: N/A

LU2_LOGMODE

Description: Defines a 1- to 8-byte character name for the 3270 log mode when one is not set for the playback GROUP statement.

Values: 1 to 8 bytes. The value must be enclosed in quotes if there are any non-alphanumeric characters.

Default: SNX32702

MODIFY_DATA_TAGE_MERGE

Description: Defines how to play back input fields with the MDT bit set to on.

Set this parameter to NO to always play back the input field appearing in the script. Set this parameter to YES to play back the real input field coming from the application program if:

The MDT bit is set to on, and
The input field in the script matches the same field in the output screen.

Values: YES or NO.

Default: NO

MAINFRAME_CODEPAGE

Description: The name of the codepage for the data on the mainframe. This parameter is utilized by both reporting and the GUI interface. The primary purpose of this parameter is to indicate the mainframe codepage for conversion of data between the mainframe and client.

Values: 1 to 8 characters.

Default: IBM-1047

Required: Yes.

MAX_HIPERSPACE_FILES

Description: For the Performance Test for VTAM component, this parameter specifies the maximum number of hiperspace memory files that the script create and audit search programs are allowed to allocate. Any system limit to the number of dataspaces and hiperspaces established by z/OS (for example, JES2 exit IEFUSI) or other customer software will remain in effect and will not be extended by this setting. This parameter is provided in case the installer wishes to further restrict Performance Test for VTAM-specific use of hiperspaces. Best performance for the Script Create and Audit Search programs is achieved when this number is higher than the highest anticipated number of concurrent sessions in a given execution. If this number is too small, multiple passes of repository data by Script Create or Audit Search must be made to process all the sessions in the input. If users are experiencing multiple VTCSUTIL-0020I messages, they can use the Review Repository function (refer to Global Recording Requests and Scripts in the Performance Test for VTAM User space) to determine the maximum number of sessions in their repository input and provide guidance as to how MAX_HIPERSPACE_FILES could be adjusted. Setting this number too high has negligible impact on Performance Test resource utilization as hiperspaces are only allocated as needed and reused when no longer needed. This parameter has no effect on the Performance Test for Mainframe Servers or Performance Test for WebSphere MQ components.

Values: Number from 2 to 2147483647 and 1 to 10 numeric digits long.

Default: 2000

PA1_KEY_OWNER

Description: Set to HIPERSTATION if you want Performance Test to process the <PA1> aid key. Set to USER to pass the <PA1> aid key to the user (the application program).

Values: HIPERSTATION or USER.

Default: HIPERSTATION

REFNAME

Description: Defines an 8-byte character string you can use to give a unique reference name to the table. Performance Test has no internal use for this parameter.

Values: 1 to 8 bytes. The value must be enclosed in quotes if there are any non-alphanumeric characters.

Default: '*DEFAULT'

SECURITY_CLASS_NAME

Description: Defines the external security product’s class name. If you do not change the default (NOSECURITY), Performance Test does not set an external security class name, resulting in a lack of external security. See Performance Test Security for more information.

Values: 1 to 8 alphanumeric characters. You can enclose the value in quotes.

Default: NOSECURITY

SECURITY_CLASS_ENTITY

Description: Performance Test uses the SECURITY_CLASS_ENTITY value as the high-level qualifier for an entity name that represents a Performance Test security entity. The system’s security package (such as RACF) uses the entity name to control and restrict access to Performance Test functions. For example, HIPER.FN.TESTING, a fully qualified entity name, is used to determine if a user has the authority for Performance Test testing. See Performance Test Security for more information.

Values: 1 to 8 alphanumeric characters. You can enclose the value in quotes.

Default: HIPER

SMTP_PROGRAM

Description: The name of the external JES writer that processed SMTP. This is typically SMTP.

Values: 1 to 8 characters.

Default: SMTP

Required: Yes.

ENABLE_CUSTOM_SIGNON_SECURITY

Description: Defines custom sign-on security. Setting this parameter to YES tells Performance Test to verify that the script signon matches the current signon. If the sign-ons match, Performance Test allows users to proceed with playback. Use this feature to prevent users from playing back other users’ scripts.

Values: YES or NO.

Default: NO

SECURITY_VOLUME

Description: Defines the external security product’s volume serial number where the data set rules reside. If your site cannot use the default (HIPERX) as the volume-serial number, change it to an acceptable volume-serial number.

Values: 1 to 6 alphanumeric characters. You can enclose the value in quotes.

Default: HIPERX

SECURITY_WILDCARD_CHAR

Description: Defines the external security product wildcard coding character. For RACF and CA Top Secret, set to HYPHEN. For CA ACF2, set to ASTERISK.

Values: HYPHEN or ASTERISK.

Default: HYPHEN

SMPE

Description: Defines a 7-byte character string that is concatenated to the unique reference name. Performance Test has no internal use for this parameter.

Values: 1 to 7 alphanumeric characters.

Default: USER

TARGET_ZONE

Description: Name of the Performance Test SMP/E target zone for this installation.

Values: 1 to 8 characters.

Default: QQFnnnT

Required:Yes.

DATE_RECALC_SATURDAY

Description: This value determines how date recalculation adjusts a result date that falls on a Saturday when the control entry specifies WEEKDAY ONLY=Y. This affects all scripts with date recalculation logic included in the REXX script processor, regardless of when the script processor ran.

Values: {NEXT|PREV}-{SUN|MON|TUE|WED|THU|FRI|SAT} | SAME-DAY

Default: NEXT-MON

DATE_RECALC_SUNDAY

Description: This value determines how date recalculation adjusts a result date that falls on a Sunday when the control entry specifies WEEKDAY ONLY=Y or WEEKDAY ONLY=S. This affects all scripts with date recalculation logic included in the REXX script processor, regardless of when the script processor ran.

Values: {NEXT|PREV}-{SUN|MON|TUE|WED|THU|FRI|SAT} | SAME-DAY

Default: NEXT-MON

VTCSMAIL_REGION_SIZE

Description: The size in megabytes to use on the REGION parameter in JCL produced executing program VTCSMAIL (E-mail Notification).

Values: Number from 0 to 9999 and 1 to 4 numeric digits long.

Default: 0

VTCSSRCH_REGION_SIZE

Description: The size in megabytes to use on the REGION parameter in JCL produced executing program VTCSSRCH (Archive Search and SIEM).

Values: Number from 0 to 9999 and 1 to 4 numeric digits long.

Default: 0

VTCSMAIN_REGION_SIZE

Description: The size in megabytes to use on the REGION parameter in JCL produced executing program VTCSMAIN (3270 and APPC Script Create).

Values: Number from 0 to 9999 and 1 to 4 numeric digits long.

Default: 0

VTCSSCLN_REGION_SIZE

Description: The size in megabytes to use on the REGION parameter in JCL produced executing program VTCSSCLN (Search Failure Cleanup).

Values: Number from 0 to 9999 and 1 to 4 numeric digits long.

Default: 0

EHSBATCH_REGION_SIZE

Description: The size in megabytes to use on the REGION parameter in JCL produced executing program EHSBATCH (3270 and APPC Batch Playback).

Values: Number from 0 to 9999 and 1 to 4 numeric digits long.

Default: 0

QQFDELET_REGION_SIZE

Description: The size in megabytes to use on the REGION parameter in JCL produced executing program QQFDELET (Archive Delete w/Segments).

Values: Number from 0 to 9999 and 1 to 4 numeric digits long.

Default: 0

REXX_REGION_SIZE

Description: The size in megabytes to use on the REGION parameter in JCL produced executing REXX programs.

Values: Number from 0 to 9999 and 1 to 4 numeric digits long.

Default: 0

TCPPBMN_REGION_SIZE

Description: The size in megabytes to use on the REGION parameter in JCL produced executing program TCPPBMN (TCP and MQ Batch Playback).

Values: Number from 0 to 9999 and 1 to 4 numeric digits long.

Default: 0

SUPPRESS_UNKNOWN_AID_COUNT

Description: The value specified limits the number of times the ETRMTSOI: UNKNOWN AID DETECTED message is written to the console during script creation.

Values: Number from 0 to 1073741824 and 1 to 10 numeric digits long.

Default: 1000000

SUPPRESS_ECHO_OF_DATA

Description: Set this parameter to YES to not echo the information provided on the DATA parameter on the GROUP statement in EHSBATCH. Use this option when sensitive data is being sent as logon data to the application.

Values: YES or NO
Default: NO

Allocation parameter defaults

The PARMLIB example member HSCMALL contains the following general parameter default Values:

SMS management class – MANAGEMENT_CLASS
SMS storage class – STORAGE_CLASS
SMS data class – DATA_CLASS
Volume serial number – VOLUME
Generic unit – UNIT
Space unit (TRK, CYL, BLK) – SPACE_UNITS
Primary space amount – PRIMARY_ALLOCATION
Secondary space amount – SECONDARY_ALLOCATION
Number of directory blocks (for those files that can be PDS) – DIRECTORY_BLOCKS
Dataset Name Prefix (17 characters maximum) – DATASET_NAME_PREFIX
Dataset Name Suffix (17 characters maximum) – DATASET_NAME_SUFFIX
Prompt for reuse (valid Values: YES or NO) – PROMPT_FOR_REUSE
Prompt to reuse preallocated data sets (valid Values: YES or NO) – REUSE_DEFAULT

Allocation parameters and their default values by file are in the DEFAULT DATASET ALLOCATION PARAMETERS section of the HSCM PARMLIB member. Update allocation defaults as needed.

Important

You can specify &SYSUID.. (including the two periods) as all of (or as part of) the value for the DATASET_NAME_PREFIX parameter within the RECORD_RECOVERY_3270 allocation block parameter. It will be replaced with the user’s userID when the file is allocated.

The following allocations can be specified:

3270 Script and Dubbing PDS – SCRIPT_DUBBING_3270
3270 Dubbing Work dataset – DUB_WORK_3270
3270 Recording recovery dataset – RECORD_RECOVERY_3270
3270 Notes temporary dataset – NOTES_TEMPORARY_3270
3270 AUTODOC – AUTODOC_3270
3270 Playback log – PLAYBACK_LOG_3270
3270 Playback comparison log – PLAYBACK_COMPARE_LOG_3270
3270 Playback journal – PLAYBACK_JOURNAL_3270
Playback REXX log – PLAYBACK_REXX_LOG
Playback summary report – PLAYBACK_SUMMARY_REPORT
Trace – TRACE
APPC script – APPC_SCRIPT
APPC Details dataset – APPC_DETAILS
APPC Conversation Log – APPC_CONVERSATION_LOG
APPC Temporary dataset – APPC_TEMPORARY_DATASET
Euro Temporary dataset – EURO_TEMPORARY
Euro Report dataset – EURO_REPORT
Global Recording Repository dataset – GLOBAL_RECORD_REPOSITORY
TCP/IP Reporting Temporary dataset – TCP_REPORTING_TEMPORARY

Performance Test for VTAM

Select product features

In addition to Domain Traveler, Performance Test for VTAM’s interactive testing facility for 3270 applications, Performance Test for VTAM offers the following features. Decide which features your site requires:

LU0 support for testing applications that use the LU0 communication protocol.
SCUT and SPASTE for copying Domain Traveler and Session Demo screen images into an ISPF Edit session.
Custom Sign-on Security for preventing users from playing back scripts containing other users’ sign-ons.

3270 Terminal definitions

Performance Test for VTAM’s Domain Traveler and unattended playback features use virtual terminals to play back recorded activity. For successful playback, the virtual terminals must have the same characteristics as your real terminals. Make sure that you modify the provided samples accordingly. If your site uses multiple terminal types, define multiple virtual terminals with unique prefixes.

Important

Performance Test for VTAM supports DBCS (Double Byte Character Set) used primarily to display Japanese Kanji characters. If your installation requires DBCS support, review DBCS Support for 3270 Applications, before installing your terminals.

VTAM Logon Mode table for 3270

Performance Test for VTAM requires a VTAM logon mode table entry. Use either the default IBM logon mode table entries in the following table or build your own table.

IBM Logon Mode Table Entries

Table Entry	SNA	Queriable	Model
D4B32782	No	No	Model 2
D4B32783	No	No	Model 3
D4B32784	No	No	Model 4
D4B32785	No	No	Model 5
NSX32702	No	Yes	Model 2
NSX32703	No	Yes	Model 3
NSX32704	No	Yes	Model 4
NSX32705	No	Yes	Model 5
D4A32782	SNA	No	Model 2
D4A32783	SNA	No	Model 3
D4A32784	SNA	No	Model 4
D4A32785	SNA	No	Model 5
SNX32702	SNA	Yes	Model 2
SNX32703	SNA	Yes	Model 3
SNX32704	SNA	Yes	Model 4
SNX32705	SNA	Yes	Model 5

Important

To use the IBM defaults, skip this step and go to Virtual Terminal APPLID Definitions for VTAM.

Important Considerations:

The terminal logon mode you enter must accurately reflect the capabilities of the terminal. Failure to do so can result in the loss of Performance Test for VTAM functionality.
IMS non-SNA terminals with improperly defined terminal logon mode table entries cause IMS to randomly issue INPUT IGNORED messages.
If your site uses a session manager, ensure that it selects a virtual terminal that accurately reflects the capabilities of the physical terminal.
If your site uses a gateway, ensure that the terminal port selected accurately reflects the terminal’s capabilities.

To build VTAM logon mode table entries:

INSTALL member EHPRMODE contains logon mode table entries for non-SNA, non-queriable Model 2, 3, 4, or 5 terminals. Modify the entries to meet your requirements, then use the sample job in INSTALL member VTAMASM to assemble and link-edit EHPRMODE.
Update the following parameters in your HSCM PARMLIB member to your site-specific equivalent logon mode entries:
- NON_SNA_NON_QUERY_LOGMODE_MODELn
- NON_SNA_QUERY_LOGMODE_MODELn
- SNA_NON_QUERY_LOGMODE_MODELn
- SNA_QUERY_LOGMODE_MODELn.

Virtual Terminal APPLID definitions for VTAM

Performance Test for VTAM uses virtual terminals to connect to domain destinations (for example, CICS). Each Performance Test for VTAM virtual terminal is defined to VTAM as an APPL. You can establish:

Dynamic APPLIDs — define a pool of APPLIDs to be assigned to users as they initiate Performance Test for VTAM sessions. For example, define EHPR0001 through EHPR0025 to provide the ability to run 25 concurrent Performance Test for VTAM sessions.
Static APPLIDs — define unique APPLIDs, the TSO user ID prefixed with the letter E, for each TSO user accessing Performance Test for VTAM.

You can also define both types of APPLIDs. Performance Test for VTAM assigns a dynamic APPLID to users who do not have a static APPLID.

To create APPLIDs:

Review the appropriate INSTALL member:
- EHPR000 provides sample dynamic APPLID definitions (EHPR000 Sample Dynamic APPLID Definition).
- EHPR001 provides a sample static APPLID definition (EHPR001 Sample Static APPLID Setup Member).
EHPR000 Sample Dynamic APPLID Definition
*********************************************************************** 00010000
*                                                                     * 00020000
*        SAMPLE VTAM LU0 APPLICATION DEFINITIONS FOR ISPF             * 00030000
*        PERFORMANCE TEST.                                            * 00040000
*                                                                     * 00050000
*        ONE APPL STATEMENT IS REQUIRED FOR EACH TSO USER             * 00060000
*        THAT CAN ACCESS A PERFORMANCE TEST VIRTUAL TERMINAL IN       * 00070000
*        A TRANSACTION PROCESSING FACILITY (TPF), SUCH AS             * 00080000
*        CICS OR IMS.                                                 * 00090000
*                                                                     * 00100000
*        SINCE THE VTAM APPLICATIONS ARE DYNAMICALLY ACQUIRED,        * 00110000
*        THE NUMBER OF APPL DEFINITIONS MUST ONLY BE EQUAL            * 00120000
*        TO THE MAXIMUM NUMBER OF TSO USERS THAT WILL USE             * 00130000
*        PERFORMANCE TEST AT ANY ONE TIME.                            * 00140000
*                                                                     * 00150000
*********************************************************************** 00190000
EHPRLU0 VBUILD TYPE=APPL                APPLICATION MAJOR NODE          00200000
*                                                                       00210000
*                                                                       00220000
EHLU0001 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00230000
EHLU0002 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00240000
EHLU0003 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00250000
EHLU0004 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00260000
EHLU0005 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00270000
EHLU0006 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00280000
EHLU0007 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00290000
EHLU0008 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00300000
EHLU0009 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00310000
EHLU0010 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00320000
EHPR001 Sample Static APPLID Setup Member
*********************************************************************** 00010000
*                                                                     * 00020000
*        SAMPLE VTAM LU0 APPLICATION DEFINITIONS FOR ISPF             * 00030000
*        PERFORMANCE TEST.                                            * 00040000
*                                                                     * 00050000
*        ONE APPL STATEMENT IS REQUIRED FOR EACH TSO USER             * 00060000
*        THAT CAN ACCESS A PERFORMANCE TEST VIRTUAL TERMINAL IN       * 00070000
*        A TRANSACTION PROCESSING FACILITY (TPF), SUCH AS             * 00080000
*        CICS OR IMS.                                                 * 00090000
*                                                                     * 00100000
*        SINCE THE VTAM APPLICATIONS ARE DYNAMICALLY ACQUIRED,        * 00110000
*        THE NUMBER OF APPL DEFINITIONS MUST ONLY BE EQUAL            * 00120000
*        TO THE MAXIMUM NUMBER OF TSO USERS THAT WILL USE             * 00130000
*        PERFORMANCE TEST AT ANY ONE TIME.                            * 00140000
*                                                                     * 00150000
*********************************************************************** 00190000
EHPRLU0 VBUILD TYPE=APPL                APPLICATION MAJOR NODE          00200000
*                                                                       00210000
*                                                                       00220000
EHLU0001 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00230000
EHLU0002 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00240000
EHLU0003 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00250000
EHLU0004 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00260000
EHLU0005 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00270000
EHLU0006 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00280000
EHLU0007 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00290000
EHLU0008 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00300000
EHLU0009 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00310000
EHLU0010 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00320000
To install these members as major nodes, copy the members to SYS1.VTAMLST.
To install definitions as minor nodes, copy the APPL statements to an existing VTAM major node.
Modify, add, or delete the definitions to meet your requirements.
If you are using IBM default logon mode entries, remove the DLOGMOD and MODETAB parameters from the middle of the APPL statements. For example, an edited:
- dynamic APPL statement looks like this:
  EHPR0001 APPL EAS=2,SESSLIM=YES
- static APPL statement looks like this:
  EUSERID1 APPL EAS=2,SESSLIM=YES
Ensure the virtual terminals are automatically activated at VTAM startup. If they are not, activate them manually by entering the following MVS operator command, where nodename is the member you created in SYS1.VTAMLST:
V NET,ACT,ID=nodename

Terminal definitions for VTAM applications

To install virtual terminals for CICS and IMS/DC:

Customize the provided samples so they mimic the terminals they are replacing and conform to your site’s installation standards.
Define a terminal for each Performance Test for VTAM APPLID defined to VTAM and in each domain destination to which a Performance Test for VTAM user connects. The terminal must have the same LU name as the VTAM APPLID. If you install 25 APPLIDs, you must make 25 terminal definitions to the domain destination.
If security is used to control access to certain terminals, ensure that Performance Test for VTAM users have proper access to the virtual terminals.

Terminal definitions for CICS

If you want to use Performance Test for VTAM’s Domain Traveler 3270 capabilities for CICS sessions, and you have defined Performance Test for VTAM virtual terminals specifically for 3270 devices, define those devices to CICS specifying 3270 terminal characteristics in a Terminal Control Table.

Important

If the CICS regions recorded by Performance Test for VTAM use auto-install, you do not have to define 3270 devices to CICS.

Create terminal IDs via one of the following:

CEDA entries
EHPR$TCT macro
TCT entries.

Important

Your CICS system programmer may need to perform this step.

CEDA entries for dynamic and static APPLIDs

The following figures shows a sample CEDA screen containing a 3270 definition for CICS.

CEDA Entries Corresponding to TCT Definitions

TYpeterm==>
........
Group==> ........

RESOURCE TYPE

DEVice ==> 3270

TERmmodel==> 2
*
*
DEVICE PROPERTIES
*
*
COPy==> Yes
DUalcasekybd==> Yes
*
*
SESSION PROPERTIES
*
*
RECeivesize==> 2048
*
*
OPERATIONAL PROPERTIES
*
*
RELreq==> Yes
DIscreq==> Yes
*
*
MESSAGE RECEIVING PROPERTIES
*
LOGOnmsg==> Yes

APPLICATION FEATURES
*
USerarealen==> 016
Ioarealen==> 00512 , 00000
UCtran==> Yes

EHPR$TCT Macro

In INSTALL members CICS000 and CICS001, macro EHPR$TCT provides a shorthand method for defining terminal IDs. Enter the LU name and terminal in the following form:

label EHPR$TCT TERM=trmidntlabel designates the LU name of the APPLID defined to VTAM. trmidnt defines the CICS terminal ID, which can be any name that is valid for the TRMIDNT operand of the DFHTCT macro.

TCT entries for dynamic APPLIDs

INSTALL member CICS000 lists sample TCT definitions for dynamic APPLIDs.

INSTALL member CICS001 lists sample TCT definitions for static APPLIDs.

Performance Vehicle CICS Terminal Definition

Performance Vehicle CICS region measurements require that a Console Terminal be installed in the targeted CICS regions. If a Console Terminal is not installed, the CICS region measurements cannot be completed, and the Performance Vehicle results could be incomplete. INSTALL member CICSCONS contains a sample Console Terminal Definition. Install this terminal into all CICS regions that the Performance Vehicle will be expected to start and stop for a performance test. Only CICS regions that the Performance Vehicle starts and stops will have performance measurements taken and used for Performance Testing.

Terminal definitions for IMS/DC

If you want to use Performance Test for VTAM’s Domain Traveler capabilities for IMS sessions, define the 3270 terminals to IMS:

Add terminals to the IMS/DC stage 1 input. Copy the sample terminal definitions from INSTALL member IMS001 (IMSLU0 Sample Definitions for Performance Test for VTAM LU0 Terminals) to the appropriate place in the IMS/DC stage 1 input, then change the sample terminal definitions to match your physical IMS terminal definitions. Define one terminal for each defined VTAM application.
INSTALL Member IMS001 Definitions for IMS Terminals
*---------------------------------------------------------------------* 00010000
*           PERFORMANCE TEST IMS TERMINAL DEFINITIONS                 * 00020000
*           NOTE: UNITYPE MUST BE LOCAL 3270                          * 00030000
*           NOTE: DEVICE TYPE MUST BE 3270-A02                        * 00040000
*           NOTE: NAMES IN NAME= OPERAND MUST MATCH THE VTAM NODE     * 00050000
*                 NAMES IN EHPR000.                                   * 00060000
*---------------------------------------------------------------------* 00070000
         TYPE UNITYPE=(3270,LOCAL),TYPE=3270-A02,SIZE=(24,80)          00080000
           TERMINAL NAME=EHPR0001,FPBUF=256,OPTIONS=(TRANRESP,NOCOPY) 00090000
             NAME HPR0001                                              00100000
           TERMINAL NAME=EHPR0002,FPBUF=256,OPTIONS=(TRANRESP,NOCOPY) 00110000
             NAME HPR0002                                              00120000
           TERMINAL NAME=EHPR0003,FPBUF=256,OPTIONS=(TRANRESP,NOCOPY) 00130000
             NAME HPR0003                                              00140000
           TERMINAL NAME=EHPR0004,FPBUF=256,OPTIONS=(TRANRESP,NOCOPY) 00150000
             NAME HPR0004                                              00160000
           TERMINAL NAME=EHPR0005,FPBUF=256,OPTIONS=(TRANRESP,NOCOPY) 00170000
             NAME HPR0005                                              00180000
           TERMINAL NAME=EHPR0006,FPBUF=256,OPTIONS=(TRANRESP,NOCOPY) 00190000
             NAME HPR0006                                              00200000
           TERMINAL NAME=EHPR0007,FPBUF=256,OPTIONS=(TRANRESP,NOCOPY) 00210000
             NAME HPR0007                                              00220000
           TERMINAL NAME=EHPR0008,FPBUF=256,OPTIONS=(TRANRESP,NOCOPY) 00230000
             NAME HPR0008                                              00240000
           TERMINAL NAME=EHPR0009,FPBUF=256,OPTIONS=(TRANRESP,NOCOPY) 00250000
             NAME HPR0009                                              00260000
           TERMINAL NAME=EHPR0010,FPBUF=256,OPTIONS=(TRANRESP,NOCOPY) 00270000
             NAME HPR0010                                              00280000
Warning
Important
You can also define the TYPE protocol as LU2.
Ensure that no duplicate definitions for the control blocks are specified in the format library concatenation. Duplicates prevent terminal connection to IMS
Finish installing Performance Test for VTAM for IMS/DC by performing normal procedures for IMS/DC generation.
If your installation uses a product that dynamically defines terminals, such as BMC Software’s Delta IMS, no further work is necessary for IMS installation.

LU0 terminal definitions

As with 3270 virtual terminals, successful playback depends on accurate virtual terminal definitions. Make sure that you modify the provided samples to mimic your real terminals. Additionally, if your site uses multiple terminal types, define multiple virtual terminals with unique prefixes.

VTAM logon mode table for LU0

Performance Test for VTAM requires a VTAM logon mode table entry. You cannot use MODETAB=EHPRMODE for LU0 devices. Use either the default IBM logon mode table entry or an equivalent. In MODETAB=ISTINCLM, the IBM default for an IBM3600 device is DLOGMOD=IBM3600. If you are using the IBM defaults, no further action is required. You are ready to create LU0 terminal definitions for VTAM. See LU0 Terminal Definitions for VTAM.

Important

Your VTAM system programmer may need to perform these steps.

Important Considerations:

The terminal logon mode you enter must accurately reflect the capabilities of the terminal. Failure to do so can result in the loss of Performance Test for VTAM functionality.
IMS non-SNA terminals with improperly defined terminal logon mode table entries cause IMS to randomly issue INPUT IGNORED messages.
If your site uses a gateway, ensure that the terminal port selected accurately reflects the terminal’s capabilities.

LU0 terminal definitions for VTAM

If the LU0 applications you are testing have security logic with terminal dependencies, define static Performance Test virtual terminals with names identical to the real terminals used by the applications.

Dynamic Application IDs

Dynamic APPLIDs involve a pool of APPLIDs defined to VTAM. For example, define EHLU0001 through EHLU0025 to give your system the ability to run 25 concurrent Performance Test for VTAM sessions. When a 26th user tries to establish a session, the message ALL PORTS BUSY appears on the Domain Traveler screen.

To create your APPLIDs:

Review INSTALL member EHPRLU0 in the following figure for examples of dynamic APPLIDs.
EHPRLU0 Sample Definition for Dynamic APPLIDs
*********************************************************************** 00010000
*                                                                     * 00020000
*        SAMPLE VTAM LU0 APPLICATION DEFINITIONS FOR ISPF             * 00030000
*        PERFORMANCE TEST.                                            * 00040000
*                                                                     * 00050000
*        ONE APPL STATEMENT IS REQUIRED FOR EACH TSO USER             * 00060000
*        THAT CAN ACCESS A PERFORMANCE TEST VIRTUAL TERMINAL IN       * 00070000
*        A TRANSACTION PROCESSING FACILITY (TPF), SUCH AS             * 00080000
*        CICS OR IMS.                                                 * 00090000
*                                                                     * 00100000
*        SINCE THE VTAM APPLICATIONS ARE DYNAMICALLY ACQUIRED,        * 00110000
*        THE NUMBER OF APPL DEFINITIONS MUST ONLY BE EQUAL            * 00120000
*        TO THE MAXIMUM NUMBER OF TSO USERS THAT WILL USE             * 00130000
*        PERFORMANCE TEST AT ANY ONE TIME.                            * 00140000
*                                                                     * 00150000
*********************************************************************** 00190000
EHPRLU0 VBUILD TYPE=APPL                APPLICATION MAJOR NODE          00200000
*                                                                       00210000
*                                                                       00220000
EHLU0001 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00230000
EHLU0002 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00240000
EHLU0003 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00250000
EHLU0004 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00260000
EHLU0005 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00270000
EHLU0006 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00280000
EHLU0007 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00290000
EHLU0008 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00300000
EHLU0009 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00310000
EHLU0010 APPL EAS=2,DLOGMOD=IBM3600,MODETAB=ISTINCLM,SESSLIM=YES       00320000
Be sure to substitute the LU0 DLOGMOD and MODETAB where required.
Install APPLIDs in the SYS1.VTAMLST data set so that they automatically activate at VTAM startup. To install the definitions as minor nodes, add only the APPL statements to an existing VTAM major node.
If APPLIDs are not automatically activated, activate them manually by entering the following MVS operator command, where nodename is the member you created in SYS1.VTAMLST:
V NET,ACT,ID=nodename

Static application IDs

If the LU0 application your are testing checks VTAM LU names hard-coded in the program and your test system allows the VTAM major node to be varied inactive without impact, define Performance Test virtual terminals with names identical to the real terminals used by the application.

To create the APPLIDs:

Create a member containing virtual terminal definitions with names identical to the real terminals used by the application. Use the logmodes that the real terminals use. For example:
HSLU000 VBUILD TYPE=APPL APPLICATION MAJOR NODE
AJK45A2E APPL EAS=2,DLOGMOD=IBM3600, MODETAB=ISTINCLN,SESSLIN=YES
LF25T14F APPL EAS=2,DLOGMOD=IBM3600, MODETAB=ISTINCLN,SESSLIN=YES
Install APPLIDs in the SYS1.VTAMLST data set so that they automatically activate at VTAM startup. To install the definitions as minor nodes, add only the APPL statements to an existing VTAM major node.
If APPLIDs are not automatically activated, activate them manually by entering the following MVS operator command, where nodename is the member you created in SYS1.VTAMLST:
V NET,ACT,ID=nodename

LU0 terminal definitions for VTAM applications

To install virtual terminals for CICS and IMS/DC:

Customize the provided samples so they mimic the terminals they are replacing and conform to your site’s installation standards.
Define a terminal for each Performance Test for VTAM APPLID defined to VTAM and in each domain destination to which a Performance Test for VTAM user connects. The terminal must have the same LU name as the VTAM APPLID. If you install 40 APPLIDs, you must add 40 terminal definitions to the domain destination.
If security is used to control access to certain terminals, ensure that Performance Test for VTAM users have proper access to the virtual terminals.

Terminal Definitions for CICS

If you want to use Performance Test for VTAM’s LU0 capabilities for CICS sessions and you have defined Performance Test for VTAM virtual terminals specifically for LU0 devices, define those devices to CICS specifying LU0 terminal characteristics in a Terminal Control Table.

Create terminal IDs via one of the following:

EHPR$TCT macro
TCT entries.

Important

Your CICS system programmer may need to perform this step.

EHPR$TCT Macro

In INSTALL member CICSLU0, macro EHPR$TCT provides a shorthand method for defining terminal IDs. Enter the LU name and terminal in the following form:

Important

If the LU0 application you are testing has logic that checks the terminal IDs, set TERM to the terminal IDs hard-coded in the application.

TCT entries for dynamic APPLIDs

In the following figure, INSTALL member CICSLU0 lists sample TCT definitions for dynamic APPLIDs.

CICSLU0 Sample TCT Definitions for dynamic APPLIDs

         MACRO                                                          00010000
&LABEL   EHPR$TCT &TERM=                                                00020000
&LABEL   DFHTCT TYPE=LDC,TRMIDNT=&TERM,NETNAME=&LABEL,                 X00030000
               TRMTYPE=3600,                                           X00090000
               ACCMETH=NONVTAM,                                        X00100000
               LDC=3600,                                               X00110000
               PGESIZE=(6,40)                                           00130000
         MEND                                                           00140000
*********************************************************************** 00150000
*                                                                     * 00160000
*        ISPF PERFORMANCE TEST LU0 TERMINAL DESCRIPTIONS              * 00170000
*                                                                     * 00180000
*        LABEL DEFINITION MUST CORRESPOND TO THE VTAM APPL NAME       * 00190000
*        DEFINED IN THE VTAM APPLICATION NODES                        * 00200000
*                                                                     * 00210000
*        TERM= OPERAND MAY BE ANY UNIQUE FOUR CHARACTER CICS          * 00220000
*              TERMINAL NAME. THIS OPERAND IS USED ON THE             * 00230000
*              TRMIDNT= OPERAND OF THE DFHTCT MACRO.                  * 00240000
*                                                                     * 00250000
*********************************************************************** 00260000
EHLU0001 EHPR$TCT TERM=E001                                             00270000
EHLU0002 EHPR$TCT TERM=E002                                             00280000
EHLU0003 EHPR$TCT TERM=E003                                             00290000
EHLU0004 EHPR$TCT TERM=E004                                             00300000
EHLU0005 EHPR$TCT TERM=E005                                             00310000
EHLU0006 EHPR$TCT TERM=E006                                             00320000
EHLU0007 EHPR$TCT TERM=E007                                             00330000
EHLU0008 EHPR$TCT TERM=E008                                             00340000
EHLU0009 EHPR$TCT TERM=E009                                             00350000
EHLU0010 EHPR$TCT TERM=E010                                             00360000

Terminal definitions for IMS/DC

If you want to use Performance Test for VTAM’s LU0 capabilities for IMS sessions, define the LU0 terminals to IMS:

Add Performance Test for VTAM terminals to the IMS/DC stage 1 input. Copy the sample terminal definitions from INSTALL member IMSLU0 (IMSLU0 Sample Definitions for Performance Test for VTAM LU0 Terminals) to the appropriate place in the IMS/DC stage 1 input, then change the sample terminal definitions to match your physical IMS terminal definitions. Define one terminal for each defined VTAM application.
Warning
Important
If the LU0 application you are testing has logic that checks the terminal IDs, set the NAME (IMS ID), at the end of the TERMINAL NAME statement, to the terminal IDs hard-coded in the application.
IMSLU0 Sample Definitions for Performance Test for VTAM LU0 Terminals
*---------------------------------------------------------------------* 00010000
*           ISPF PERFORMANCE TEST LU0 TERMINAL DEFINITIONS            * 00020000
*           NOTE: NAMES IN NAME= OPERAND MUST MATCH THE VTAM NODE     * 00050000
*                 NAMES IN EHPRLU0.                                   * 00060000
*---------------------------------------------------------------------* 00070000
           TYPE UNITYPE=(3601),SIZE=(6,40)                             00080000
           TERMINAL NAME=EHLU0001,OPTIONS=(NOASR,NOFES,NRNR),M         00090000
             NAME HLU0001                                              00100000
           TERMINAL NAME=EHLU0002,OPTIONS=(NOASR,NOFES,NRNR),M         00110000
             NAME HLU0002                                              00120000
           TERMINAL NAME=EHLU0003,OPTIONS=(NOASR,NOFES,NRNR),M         00130000
             NAME HLU0003                                              00140000
           TERMINAL NAME=EHLU0004,OPTIONS=(NOASR,NOFES,NRNR),M         00150000
             NAME HLU0004                                              00160000
           TERMINAL NAME=EHLU0005,OPTIONS=(NOASR,NOFES,NRNR),M         00170000
             NAME HLU0005                                              00180000
           TERMINAL NAME=EHLU0006,OPTIONS=(NOASR,NOFES,NRNR),M         00190000
             NAME HLU0006                                              00200000
           TERMINAL NAME=EHLU0007,OPTIONS=(NOASR,NOFES,NRNR),M         00210000
             NAME HLU0007                                              00220000
           TERMINAL NAME=EHLU0008,OPTIONS=(NOASR,NOFES,NRNR),M         00230000
             NAME HLU0008                                              00240000
           TERMINAL NAME=EHLU0009,OPTIONS=(NOASR,NOFES,NRNR),M         00250000
             NAME HLU0009                                              00260000
           TERMINAL NAME=EHLU0010,OPTIONS=(NOASR,NOFES,NRNR),M         00270000
             NAME HLU0010                                              00280000
Ensure that no duplicate definitions for the control blocks are specified in the format library concatenation. Duplicates prevent terminal connection to IMS.
Finish installing Performance Test for VTAM for IMS/DC by performing normal procedures for IMS/DC generation.
If your installation uses a product that dynamically defines terminals, such as BMC Software’s Delta IMS, no further work is necessary for IMS installation.

Application-specific terminal ID tables

If the LU0 application you are testing performs a table look-up using the terminal ID, add Performance Test virtual terminals (or their associated termids) to the application’s terminal ID table.

Reporting asset library

This step creates a reporting assets library and populates it with members containing sample reporting statements and JCL.

Open member HSPBCOPY found in the Performance Test INSTALL library.
On 'SET SAMP =', specify the fully qualified data set name of the Performance Test sample library (SQQFSAMP).
On 'SET REPT=', specify a data set name for the reporting asset library being created.
On 'SET DISK=', specify the DASD esoteric (unit name) to be used.
Submit the Job.

Additional features

Other optional Performance Test for VTAM features include:

SCUT and SPASTE for copying Domain Traveler and Session Demo screen images into ISPF Edit
Custom Sign-on Security for preventing users from playing back scripts containing other users’ user ID and password.

This section explains how to enable these features.

SCUT and SPASTE (Optional)

Performance Test for VTAM provides the SCUT command for copying screen images from Domain Traveler and Session Demo, into the ISPF clipboard. SPASTE pastes them into an ISPF Edit session.

To enable SCUT and SPASTE, copy the SPASTE and SPASTEX members of the INSTALL library to a library in the user’s SYSPROC DD concatenation.

Performance Test for VTAM Primary Option menu

You can alter the short and long names and the title on the Performance Test for VTAM Primary Option Menu by editing sample library data set ETRM@xxx (where xxx is the 3-character value from the PRIMARY_OPTION_MENU_LANGUAGE= parameter on the $PNLOPT TYPE=ENTRY macro), then reassembling.

The ETRM@xxx source consists of a series of $PNLOPT macros. To alter the title, short name, and/or long name, change the text after the following keywords:
- TITLE = (maximum characters: 80)
- STEXT =(maximum characters: 25)
- LTEXT =(maximum characters: 50).
Reassemble and link-edit ETRM@xxx. Sample JCL is in INSTALL member ASSEMPNL.

Number of 3270 Virtual Terminals (APPLIDs)

If you increase the number of Performance Test for VTAM 3270 virtual terminals (for example, increasing the number of available Performance Test for VTAM users), you may also have to modify the terminal definitions in your domain destinations (CICS and IMS regions) to support the additional users. If the CICS regions use auto-install, this is not necessary.

Prefix of 3270 Virtual Terminals (APPLIDs)

If you changed the prefix of the Performance Test for VTAM APPLIDs during Guided Configuration (for example, EHPR0001 to CUST0001), you also need to make the following modifications:

Remember to make any corresponding changes to the CICS and IMS definitions.
Set parameter VIRTUAL_TERMINAL_PREFIX in the HSCM PARMLIB member to the new prefix. For example: VIRTUAL_TERMINAL_PREFIX=CUST

Important

Be sure to add the variable PREFIX(cccc), where cccc is the new prefix, to your unattended mode batch job CONTROL statements.
The default prefix is EHPR.
The prefix and suffix together cannot exceed eight bytes.

Suffix of 3270 Virtual Terminals (APPLIDs)

If you changed Performance Test for VTAM APPLID suffixes during Guided Configuration (for example, EHPR0001 to EHPR01), make these additional changes:

Remember to make any corresponding changes to the CICS and IMS definitions.
Set variable VIRTUAL_TERMINAL_SUFFIX_LENGTH.

Important

The variable SUFFIX(n), where n is the length of the new suffix, must be added to your unattended mode batch job CONTROL statements. The default suffix length is four.
The length of the suffix has a direct impact on the number of terminals that can be defined. For example, suffix=2 implies a maximum of 99 terminals.
The prefix and suffix together cannot exceed eight bytes.

Domain Traveler customization

By default, the Domain Traveler screen presents a field for the user to enter the domain destination ID. You can customize the Domain Traveler screen to present a list of valid domain destination IDs for the user to choose from, or you can build a custom list screen that the user can access by typing a slash (/) in the Domain Destination field. The user can either enter the ID or select it from the list.

This section provides instructions for both customizing options.

Domain Traveler Screen

To customize the Domain Traveler screen:

Modify the ETRMCUST member in the SQQFPENU library. Change the domain destination descriptors in the screen body and add the domain destination names to the screen’s selection logic.
Warning
Important
You may want to make a backup copy of ETRMCUST before modifying it. Also, you can give the modified member a unique name if you prefer.
Set the value of the INITIAL_DOMAIN_TRAVELER_PANEL variable in the HSCM PARMLIB member to the customized screen member. For example:
INITIAL_DOMAIN_TRAVELER_PANEL='ETRMCUST' /* INITIAL DOMAIN TRAVELER PANEL*/

Custom Domain Destination List screen

Domain Traveler is already equipped with logic to present screen ETRMUDF1 when the user enters a slash (/) in the Domain Destination field and presses Enter. Simply modify member ETRMUDF1 in the SQQFPENU library. This library also contains the sample member ETRMUDF2, which offers a template for the screen image, sample list-selection logic, and sample logic for presenting certain screens to specific users.

Terminal prefix assignments in a VTAM multi-node environment

If you need to run Performance Test for VTAM in a VTAM multi-node configuration, define your VTAM applications (APPLIDs) to each system running Performance Test for VTAM. On each applicable node, perform the steps from 3270 Terminal Definitions.

You also need to assign a unique terminal prefix to each node to ensure each terminal in the network has a unique terminal ID. This section explains how to establish the default prefix for each node.

Performance Test for VTAM automatically sets the variable ETRMSSID to the four-character system management facility (SMF) system ID.

DBCS support for 3270 applications

If your site uses double-byte character set (DBCS) terminals to support Kanji, the following options are available:

Alphanumeric terminal support,
DBCS terminal support, or
DBCS and alphanumeric terminal support.

Alphanumeric terminals only

This option requires no special considerations.

DBCS terminals only

In the HSCM PARMLIB member, change the following:

ENABLE_DBCS=YES /*ENABLE DBCS SUPPORT */During the Guided Configuration, when you are instructed to copy EHPR000 from the INSTALL to SYS1.VTAMLST, copy member EHPRDBCS instead.

When defining the terminals to CICS, define the DBCS attributes for Performance Test terminals. To use Performance Test with TSO, IMS/DC, and ROSCOE, no special terminal definitions are required. Those domain destinations dynamically determine if the terminal has DBCS capabilities and uses them if they are present.

Both DBCS and alphanumeric terminals

In the HSCM PARMLIB member, change the following:

ENABLE_DBCS=YES /*ENABLE DBCS SUPPORT */

INITIAL_DOMAIN_TRAVELER_PANEL=ETRMBOTH /* INITIAL DOMAIN TRAVELER PANEL */ETRMBOTH is the DBCS version of the Domain Traveler screen. If your installation is going to create a customized Domain Traveler screen, you can use member ETRMCUSD from the SQQFPENU as an example. During the Guided Configuration, when you are instructed to copy EHPR000 from the INSTALL to SYS1.VTAMLST, copy member EHPRBOTH from INSTALL instead.

To support both DBCS and alphanumeric terminals, Performance Test generates twice the number of terminals. They are defined in the INSTALL member EHPRBOTH. This means that the number of terminals defined to the domain destinations—such as CICS and IMS/DC—must be doubled. Performance Test generates terminal names:

Terminal Name	Description
EHPR0001 through EHPR0010	Definitions for alphanumeric terminals.
DHPR0001 through DHPR0010	Definitions for DBCS terminals.

If you change the prefixes of the terminals, change the prefixes in the HSCM PARMLIB member. The new prefixes default to EHPR for alphanumeric terminals and DHPR for DBCS terminals. To change the definitions, add/replace the following parameters in the HSCM PARMLIB member:

VIRTUAL_TERMINAL_PREFIX_ALPHA='alpha-prefix' /* Four character alpha term prefix */
VIRTUAL_TERMINAL_PREFIX_DBCS='dbcs-prefix' /* Four character DBCS terminal prefix */When defining the terminals to CICS, define the DBCS attributes for Performance Test DBCS terminals.

Important

When you define both DBCS and alphanumeric terminals, the user has the choice to enable DBCS mode or not. The following field on the DBCS version of the Domain Traveler screen implements this option:

{{code language="none"}}
DBCS MODE ENABLED ===> (Y - Yes, N - No)
{{/code}}

Specialized 3270 recording methods

The following section describes two specialized 3270 recording methods:

user ID Global Recording with RACF, ACF2, or Top Secret
end-user recording.

Global recording by User ID

RACF and ACF2 provide exits that enable Global Recording by user IDs. Performance Test provides RACF and ACF2 exit routines in module form.

For CICS user IDs, the CICS application must have a SIT table with DFHSIT parameter ESMEXITS=INSTLN specified. You can only specify the ESMEXITS parameter in the SIT table (no override permitted).

Important

When using these security packages, Global Recording will not record users who are not defined in these security packages.

The RACF and ACF2 exits are dynamically activated using the Global Recording started task only if you have chosen the SVUSEREC subtask attach. If you do not activate this subtask, security exits are not activated.

If this exit activation method does not conform to your security standards, do not activate the user ID option using the USERID_TRACKING specification. The exits do not have to be active in order for the remaining components of Global Recording to function properly. In other words, if you choose not to activate this option, you cannot record by user ID, but you can still initiate Global Recordings by terminal LU or application ID names.

RACF Exits

The dynamically activated exits for RACF are ICHRIX01 and ICHRIX02. See the IBM manual System Programming Library: RACF for more information.

The dynamic RACF exit installation process used by Performance Test for Global Recording by user ID allows a more simplified installation by removing the following requirements:

Access to sensitive MVS system data sets
Inserting Performance Test-supplied code into the ICHRIXnn modules
Assembling and linking the ICHRIXnn modules
Moving the modules to an MVS LPA library
Performing an MVS IPL.

Important

Dynamic installation does affect the RACF Data Security Monitor (DSMON). The monitor checks the RACF vector table (RCVT) to ensure that the exits addressed in the table are ICHRIX01 and ICHRIX02. When DSMON detects that the table does not address these exits, it interprets this as a security integrity exposure. DSMON detects this exposure only if it is run while the Global Recording started task is active. Performance Test installs the exits during initialization and removes them during shutdown.

To alleviate security concerns, we recommend that you limit access to the Global Recording PROC to the systems personnel responsible for maintenance.

Installing the dynamic exit for RACF involves four modules: SVRACINT, SVRACDEL, SVRACON1, and SVRACON2. These modules are on the product media as separate load modules.

RACF Dynamic Exit Modules

Module	Description
SVRACINT	This module installs the Performance Test RACF exits for ICHRIX01 and ICHRIX02. The routine works by locating the RACF vector table (RCVT) and replacing or adding exit addresses into the RCVT. The routine also saves the address of any installed exits that Performance Test replaces. These exits run after Performance Test exit routines have finished processing.
SVRACDEL	This routine removes the Performance Test RACF exits installed by SVRACINT. The de-installation works by locating the RCVT and replacing the exit addresses with the address of any installed exits saved during installation.
SVRACON1	This is the RACF post-processing exit. This routine processes any logon request and puts the information in the Performance Test user ID tracking table. After processing, Performance Test invokes the next exit (the address that was saved during installation).
SVRACON2	This is the RACF preprocessing exit. This routine processes any logoff request and stores the information in the Performance Test user ID tracking table. After processing Performance Test invokes the next exit (the address that was saved during installation).

ACF2 Exits

The dynamically activated exits for ACF2 are LGNPXIT, SEVPRE, and SEVPOST. Computer Associates’ CA-ACF2 MVS System Programmer Guide provides information about these exits. Review the security rules for adding a Global Recording request listed the Function Security Matrix. It is important to ensure the necessary entities are properly defined.

ACF2 Exit Modules

Module	Description
SVACFINT	This module installs the Performance Test ACF2 exits for SEVPRE, SEVPOST, and LGNPXIT. The routine works by locating the ACF2 vector table (ACCVT) and replacing or adding exit addresses into the ACCVT. The routine also saves the address of any installed exits that Performance Test replaces. These exits run after Performance Test exit routines have finished processing.
SVACFDEL	This routine removes the Performance Test ACF2 exits installed by SVACFINT. The de-installation works by locating the ACCVT and replacing the exit addresses with the address of any installed exits saved during installation.
SVACFON1	This is the ACF2 post-processing exit. This routine processes any logon request and puts the information in the Performance Test user ID tracking table. After processing, Performance Test invokes the next exit (the address that was saved during installation).
SVACFON2	This is the ACF2 preprocessing exit. This routine processes any logoff request and stores the information in the Performance Test user ID tracking table. After processing Performance Test invokes the next exit (the address that was saved during installation).
SVACFON3	This is an ACF2 post-processing exit. This routine processes any logon request from TSO and puts the information in the Performance Test user ID tracking table. After processing, Performance Test invokes the next exit (the address that was saved during installation).

Note

The source field must contain the VTAM terminal LU the user is signing on from. In ACF2, activate the CICS source name modification exit by specifying EXIT SOURCE=YES, and use the sample for this exit as provided with ACF2. You cannot use a custom exit in this case.
The use of 3270 session managers such as CL/Supersession, TPX, and Teleview require proper setup. It may be necessary to consult with both your VTAM systems programmer (to ensure proper terminal/user ID pass through) and your security administrator (to validate the proper handling of the VTAM data streams within your security package).

Top Secret Exits

Performance Test provides Top Secret exit routines in source form.

Important

If you need to record by user ID and you have another type of security product, you can use the source form of the Top Secret exits as a coding example.

Performance Test supports the Global Recording of Top Secret user IDs by modifying the Top Secret installation exit TSSINSTX. Computer Associates’ CA Top Secret Implementation General space for MVS documents TSSINSTX. Modifying TSSOMSTX takes five actions:

Enable Exit Points

Enable three exit points by changing the appropriate exit constant from AL1 (#####NO) to AL1 (#####YES). The exit points you need to enable are described in the following table.

Insert Macros Provided with Performance Test for VTAM

TSSINSTX Exit Points

Entry Label	Code	Description
TERM	20	Job (address space) termination
POSTINIT	24	Job/session initiation complete
SESSEND	40	Individual session termination

Performance Test provides two macros ($SVTOPX1 and $SVTOPX2) in the INSTALL library. Insert them into TSSINSTX (TSSINSTX Macros). If site-specific code already exists at these insertion points, it is very important to ensure that the Performance Test macros ($SVTOPX1 and $SVTOPX2) are inserted in the proper place.

Assemble and Link-Edit TSSINSTX

The load module must be reentrant and reside in a link-list library. Remember to use the INSTALL as a macro library.

Activate TSSINSTX

Activate the exit using the CA Top Secret control option EXIT(ON).

Setting CA Top Secret as the security system

Set CA Top Secret as the security system in the Global Recording startup parameters as follows: EXTERNAL_SECURITY_PRODUCT=TOPSEC. Complete the instructions provided in Securing Access to Performance Test Functions.

TSSINSTX Macros

*---------------------------------------------------------------------
*PROCESS JOB TERMINATION
*---------------------------------------------------------------------
SPACE
TERM    DS    0H
        $SVTOPX1
         B    EXIT0
*--------------------------------------------------------------------
*PROCESS SESSION TERMINATION
*--------------------------------------------------------------------
    SPACE
SESSEND    DS    0H
           $SVTOPX1
           B    EXIT0
$SVTOPX2 must be inserted after label POSTINIT as shown below
*-------------------------------------------------------------------
*PROCESS JOB/SESSION POST-INITIATION
*-------------------------------------------------------------------
    SPACE
POSTINIT    DS      0H
            $SVTOPX2
            B    EXIT0

End-User Recording

End-user recording allows individuals with no knowledge of TSO to create scripts. End-user recording eliminates all interaction with TSO except during logon.

The end-user logs on to an ID established to perform the recording. The system programmer sets up the ID and logon procedure.

The end-user never sees TSO screens after the initial LOGON. When the user logs off the domain destination, the TSO session automatically logs off and returns the terminal to VTAM.

End-User Recording Example

To initiate end-user recording, the user enters the logon sequence for a special TSO user ID set up by a systems programmer.

Initial Logon Screen

Welcome to Compuware Corporation Enter logon sequence. Termid: L003T007
logon tsohp01

After logging on, the following screen appears. The end-user enters their password.

TSO/E Logon screen

------------------------------- TSO/E LOGON ----------------------------------
PF1/PF13 ==> Help   PF3/PF15 ==> Logoff    A1 ==> Attention    A2 ==> Reshow
Request specific HELP information by entering a ? in any entry field.
    ENTER LOGON PARAMETERS BELOW:                   RACF LOGON PARAMETERS:

    USERID    ===> TSOHP01

    PASSWORD ===>                                  NEW PASSWORD ===>

    PROCEDURE ===> IKJHPERA                         GROUP IDENT ===>

    ACCT NMBR ===> HPERA

    SIZE      ===> 4096

The logon sequence then continues, issuing site-specific logon messages.

Logon Messages Screen

TSOHP01 LOGON IN PROGRESS AT 12:59:56 ON JANUARY 2, 2015
NO BROADCAST MESSAGES

Instead of a TSO or ISPF screen, the end-user sees a regular domain destination. Performance Test for VTAM has automatically begun recording.

Performance Test for VTAM Recording Process

***AEH2212   WELCOME TO CICS/MVS *** 13:02:23

       CCC    IIII     CCC     SSS           MMM    MMM   VVV   VVV   SSS
      CCCCC    II     CCCCC   SSSSS          MMMM MMMM    VV   VV   SSSSS
     CC CC    II    CC CC   SS SS         MM MMMM MM    VV   VV   SS SS
     CC        II    CC        SS      ***   MM MM MM    VV   VV    SS
     CC        II    CC          SS    ***   MM      MM    VV   VV      SS
     CC CC    II    CC CC   SS SS         MM      MM     VV VV    SS SS
      CCCCC    II     CCCCC   SSSSS          MM      MM      VVV     SSSSS
       CCC    IIII     CCC     SSS          MMMM    MMMM      V       SSS

When you issue the normal logoff, which for CICS might be CESF LOGOFF, the terminal returns to VTAM and recording stops. The recording is now ready for use in regression or stress testing runs.

End-user recording setup

You can set up end-user recording by creating one or more TSO user IDs that access a CLIST to automatically start Performance Test for VTAM. You can use the CLIST ENDUSER in the INSTALL data set for this purpose. The CLIST shows:

Name of the domain destination
Name of the script data set
Name of the member to be recorded
VTAM LOGMODE
Logon data to pass to the domain destination.

This gives you complete control over the end-user environment.

Script Processors Parameters

Performance Test for VTAM offers a variety of script processors to automate common script editing tasks, such as date recalculation and data replacement. Review the following script processor parameter settings in the SCRIPT PROCESSOR EXECUTION PARAMETERS section of the HSCM PARMLIB member, to ensure they support your environment. Be sure EXEC_PDS points to the data set name of the SQQFEXEC library.

EXEC_PDS

Description: Data set name of the library/data set that contains the EXECs used to run the script processor. Be sure this parameter points to the data set name of the SQQFEXEC library.

SP_SYSOUT

Description: Sets the default value for the SYSOUT class field on the Background Execution screen. Default is an asterisk (*).

Default: Asterisk (*)

RGN_SIZE

Description: Region size of the background execution script processor job.

Values: 2 to 6 characters.

Default: 4096 KB

LOW_YEAR

Description: Used when handling year portions of date fields. If the year field is a two-digit year and the year is equal to or less than LOW_YEAR, Performance Test for VTAM presumes the year to be 2000. For example, if the script processor encounters the date 08/25/01, it assumes the year is 2001 (not 1901).

Values: Number from 0 to 99.

Default: 30

MMDDY_FLOATING_WINDOW

Description: Used by Date Recalculation for the date format MMDDY. This value calculates the starting year of a ten year window used to determine the actual year (YYYY) from the single digit year. The default value is 4. This value is subtracted from the current year to determine the starting year of the window. For example, if the current year is 2006 and default value is 4, then the ten year window is 2002 (2006 - 4) to 2011.

Default: 4

HIGH_YEAR

Description: Used when handling the year portion of date fields. If the year field is a two-digit year and the year is equal or greater than HIGH_YEAR, Performance Test for VTAM presumes the year to be 1900. For example, if the script processor encounters the date 08/25/96, it assumes the year is 1996 (not 2096).

Values: Number from 0 to 99.

Default: 80

Important

When the script processor determines if a field is a date and the year portion is two digits, the year field does not match the valid criteria if its value is between LOW_YEAR and HIGH_YEAR. For example, if LOW_YEAR is 20 and HIGH_YEAR is 80, and the script processor encounters a field that has the value 032945, the script processor determines that the year field does not match the criteria, and therefore, will not change the date.

CURRENT_PAGE_ROW

Description: Used by the REXX script processor list processing function when the end-of-list identifier is a current page/total page counter. This value specifies the screen row where the current page field appears.

For example, when SAP applications show a list screen, the bottom right corner of the screen has a value nn/nn. This is the current page/total page counter. 07/07 indicates page 7 of 7.

Values: Number from 1 to 43.

Default: 24

CURRENT_PAGE_COL

Values: Number from 1 to 132.

Default: 76

CURRENT_PAGE_LEN

Description: Used by the REXX script processor list processing function when the end-of-list identifier is a current page/total page counter. This value specifies the number of characters in the length of the current page field.

Values: Number from 1 to 7.

Default: 2

TOTAL_PAGE_ROW

Description: Used by the REXX script processor list processing function when the end-of-list identifier is a current page/total page counter. This value specifies the screen row where the total page field appears.

For example, when SAP applications show a list screen, the bottom right corner of the screen shows nn/nn. This is the current page/total page counter. 07/07 indicates page 7 of 7.

Values: Number from 1 to 43.

Default: 24

TOTAL_PAGE_COL

Values: Number from 1 to 132.

Default: 79

TOTAL_PAGE_LEN

Description: Used by the list processing function of the REXX script processor when the end-of-list identifier is a current page/total page. This value specifies the number of characters in the length of the total page field.

Values: Number from 1 to 7.

Default: 2

Security Script Processor Exit Routine

If your site requires it, you can limit access to Security Script Processor functions to certain users only. To limit access, open SQQFEXEC member SPCPWSCK and follow the instructions within to restrict access to the Security Script Processor at your site.

Online Testing parameters

Domain Traveler, Quick Play, and Global Recording use the online testing parameters listed in this section. These parameters reside within the HSCM PARMLIB member. Review each parameter to ensure it supports your environment.

VIRTUAL_TERMINAL_MODEL_NUMBER

Description: Virtual terminal 3270 model.

Values: Number from 1 to 5.

Default: 2

ENABLE_VIRUTAL_TERMINAL_QUERY_SUPPORT

Description: Enable terminal query support for the virtual terminal.

Values: YES or NO.

Default: YES

ENABLE_VIRUTAL_TERMINAL_SNA_SUPPORT

Description: Enable SNA support for the virtual terminal.

Values: YES or NO.

Default: YES

NON_SNA_NON_QUERY_LOGMODE_MODEL1

Description: Logmode for a non-SNA, non-queriable model 1.

Values: 1 to 8 characters.

Default: D4B32781

NON_SNA_NON_QUERY_LOGMODE_MODEL2

Description: Logmode for a non-SNA, non-queriable model 2.

Values: 1 to 8 characters.

Default: D4B32782

NON_SNA_NON_QUERY_LOGMODE_MODEL3

Description: Logmode for a non-SNA, non-queriable model 3.

Values: 1 to 8 characters.

Default: D4B32783

NON_SNA_NON_QUERY_LOGMODE_MODEL4

Description: Logmode for a non-SNA, non-queriable model 4.

Values: 1 to 8 characters.

Default: D4B32784

NON_SNA_NON_QUERY_LOGMODE_MODEL5

Description: Logmode for a non-SNA, non-queriable model 5.

Values: 1 to 8 characters.

Default: D4B32785

NON_SNA_QUERY_LOGMODE_MODEL2

Description: Logmode for a non-SNA, queriable model 2.

Values: 1 to 8 characters.

Default: NSX32702

NON_SNA_QUERY_LOGMODE_MODEL3

Description: Logmode for a non-SNA, queriable model 3.

Values: 1 to 8 characters.

Default: NSX32703

NON_SNA_QUERY_LOGMODE_MODEL4

Description: Logmode for a non-SNA, queriable model 4.

Values: 1 to 8 characters.

Default: NSX32704

NON_SNA_QUERY_LOGMODE_MODEL5

Description: Logmode for a non-SNA, queriable model 5.

Values: 1 to 8 characters.

Default: NSX32705

SNA_NON_QUERY_LOGMODE_MODEL1

Description: Logmode for an SNA, non-queriable model 1.

Values: 1 to 8 characters.

Default: D4A32781

SNA_NON_QUERY_LOGMODE_MODEL2

Description: Logmode for an SNA, non-queriable model 2.

Values: 1 to 8 characters.

Default: D4A32782

SNA_NON_QUERY_LOGMODE_MODEL3

Description: Logmode for an SNA, non-queriable model 3.

Values: 1 to 8 characters.

Default: D4A32783

SNA_NON_QUERY_LOGMODE_MODEL4

Description: Logmode for an SNA, non-queriable model 4.

Values: 1 to 8 characters.

Default: D4A32784

SNA_NON_QUERY_LOGMODE_MODEL5

Description: Logmode for an SNA, non-queriable model 5.

Values: 1 to 8 characters.

Default: D4A32785

SNA_QUERY_LOGMODE_MODEL2

Description: Logmode for an SNA, queriable model 2.

Values: 1 to 8 characters.

Default: SNX32702

SNA_QUERY_LOGMODE_MODEL3

Description: Logmode for an SNA, queriable model 3.

Values: 1 to 8 characters.

Default: SNX32703

SNA_QUERY_LOGMODE_MODEL4

Description: Logmode for an SNA, queriable model 4.

Values: 1 to 8 characters.

Default: SNX32704

SNA_QUERY_LOGMODE_MODEL5

Description: Logmode for an SNA, queriable model 5.

Values: 1 to 8 characters.

Default: SNX32705

RECORD_LOGICAL_APPLICATION_SCREENS

Description: Record logical application screens. Normally, Performance Test records each data stream sent by the application as a message. Sometimes this results in several output messages in the script when the user sees only one screen.

Values: YES or NO.

Default: NO

VIRTUAL_TERMINAL_PREFIX_ALPHA

Description: Prefix for ALPHA virtual terminals. Default is EHPR. For more information, see DBCS Support for 3270 Applications.

Values: 1 to 7 characters.

Default: EHPR

Required: Yes.

MAXIMUM_BIND_TIME

Description: Bind time limit. If the amount of time to connect to the TPF exceeds this limit, Performance Test issues message EMTRM064. For batch mode, see the BIND parameter.

Values: Number from 1 to 9999.

Default: 1500 (15 seconds)

COMPRESS_ZOOM_MODE_IO

Description: Compress zoom mode input and output. Specifies to strip nulls of data in zoom mode.

Values: YES or NO.

Default: YES

ENABLE_DBCS

Description: Enable DBCS support. Always set this parameter to NO for non-double byte character support systems, or you will waste CPU cycles.

Values: YES or NO.

Default: NO

VIRTUAL_TERMINAL_PREFIX_DBCS

Description: Prefix for DBCS virtual terminals. For more information, see DBCS Support for 3270 Applications.

Values: 1 to 7 characters.

Default: DHPR

GLOBAL_RECORD_REQUEST_FILE

Description: Name of the Global Recording request file.

Values: 1 to 44 characters.

Default: COMPWARE.QQFnnn.GRREQ

Required: Yes.

TOGGLE_ZOOM_MODE_PFKEY

Description: Zoom key.

Values: PF1 to PF24.

Default: PF23

MAJOR_ENQUEUE_NAME_RECORD

Description: Major name used when Performance Test enqueues on a recording file.

Values: 1 to 8 characters.

Default: EHPRSTAT

ENABLE_DOMAIN_TRAVELER_IMS_SUPPORT

Description: Enable IMS support. This includes checking for premature keyboard unlock.

Values: YES or NO.

Default: YES

PREMATURE_KEYBOARD_UNLOCK_TIMER

Description: Premature keyboard unlock time limit. This is for applications such as IMS, which may unlock the keyboard before the output screen is completely written. If a premature keyboard unlock condition occurs, and waits for more than this time limit, Performance Test issues message EMTRM054 and continues.

Parameter ENABLE_DOMAIN_TRAVELER_IMS_SUPPORT turns off IMS support such as premature keyboard unlock checking. Also, if you are not doing any IMS application testing, this can be set to 0. For batch mode, see the KEY2 parameter.

Values: Number from 1 to 9999.

Default: 2500 (25 seconds)

REPORT_TITLE_COMPANY_NAME

Description: Company name to use on all report titles.

Values: 1 to 44 characters.

Default: ---------COMPUWARE CORPORATION----------

SESSION_DEMO_NEXT_KEY

Description: Default aid key to move to the next screen during Session Demo.

Values: PF1 to PF24.

Default: PF11

VIRTUAL_TERMINAL_PREFIX

Description: Prefix for non-DBCS virtual terminals. For batch mode, see the PREFIX parameter. For more information, see Prefix of 3270 Virtual Terminals (APPLIDs).

Values: 1 to 7 characters.

Default: EHPR

Required: Yes.

INITIAL_DOMAIN_TRAVELER_PANEL

Description: Initial Performance Test for VTAM Domain Traveler panelID. You can change this to customize your own screen.

Values: 1 to 8 characters.

Default: ETRM000

SESSION_DEMO_PREV_KEY

Description: Default aid key to return to the previous screen during Session Demo.

Values: PF1 to PF24.

Default: PF10

ENABLE_REXX_IN_SCRIPTS

Description: Enable REXX processing. Setting this parameter to NO results in more efficient (CPU and memory) execution of scripts. Do not set this to NO if your scripts contain REXX. For batch mode, see the REXXOFF control card keyword.

Values: YES or NO.

Default: YES

STRIP_NULLS_OFF_PROTECTED_MDT_FIELDS

Description: Superoptimizer translate flag. Specifies to strip nulls off of protected MDT fields.

Values: YES or NO.

Default: NO

VIRTUAL_TERMINAL_SUFFIX_LENGTH

Description: The suffix for the virtual terminals. For batch mode, see the SUFFIX parameter. See Suffix of 3270 Virtual Terminals (APPLIDs) for more information.

Values: Number from 1 to 7.

Default: 4

TGET_DELAY_INTERVAL

Description: The TGET delay interval. When the TGET no wait is enabled, it sets the time (in hundredths of a second) that Performance Test waits between TGETs.

Values: Number from 1 to 9999.

Default: 022

SECONDARY_WRITE_TIME_LIMIT

Description: Time limit for secondary writes. Performance Test checks for secondary writes every nnn seconds.

Values: Number from 1 to 9999.

Default: 025

SECONDARY_WRITE_TIME_DELAY_MULTIPLER

Description: Time delay multiplier. Performance Test checks nnn times for a secondary write.

Values: Number from 1 to 9999.

Default: 008

ENABLE_TGET_NOWAIT_ZOOM_MODE

Description: Enables the TGET no wait when in zoom mode.

Values: YES or NO.

Default: YES

STRIP_TRAILING_BLANKS_NONZOOM

Description: Strip trailing blanks. Tells Performance Test to strip blanks off of data in non-zoom (ISPF) mode. The effect of STRIP_TRAILING_BLANKS_NONZOOM varies based on the value of the ESHDFLT parameter FIELD_TRAILER. See FIELD_TRAILER for more information. Options are:

KEEPONE = Keep one trailing blank
KEEPALL = Keep all trailing blanks
NONE = Do not keep any trailing blanks.

Values: KEEPONE, KEEPALL, or NONE.

Default: NONE

TGET_DELAY_INTERVAL_REPEAT_COUNT

Description: The TGET delay interval repeat count (the number of times Performance Test executes a TGET at the above interval).

Values: Number from 1 to 9999.

Default: 030

TGET_DELAY_INTERVAL_SWAP_TIME

Description: The TGET delay interval swap time. After the repeat count is exceeded, Performance Test does TGETs every nnn seconds.

Values: Number from 1 to 9999.

Default: 110

DOMAIN_TRAVELER_USE_TERMINAL_QUERY

Description: Tells Performance Test to use the physical terminal query. Performance Test normally responds to a terminal query with a hard-coded response. Setting this parameter to YES allows Performance Test to respond to the query with the same data that would be sent from the current physical terminal. This often helps when the application has complex extended attributes screens that Performance Test cannot handle. However, setting this parameter to YES may result in scripts incompatible with batch playback.

Values: YES or NO.

Default: NO

USE_USA_DATE_FORMAT

Description: Uses the US date format. Sets the date display format in the reports that the tool creates and in the SYSPRINT messages it issues. YES sets the date format to MONTH/DAY/YEAR. NO sets the date format to YEAR/MONTH/DAY.

Values: YES or NO.

Default: YES

KEYBOARD_UNLOCK_TIMER

Description: Keyboard unlock time limit. If the application response time exceeds this limit, Performance Test sends message EMTRM051, ignores the output it was waiting for, and continues. For batch mode, see the KEYU control card keyword.

Values: Number from 1 to 9999.

Default: 4500 (45 seconds)

Performance Test for Mainframe Servers

Product features

With Performance Test for Mainframe Servers, you can record and playback APPC, LU0, LU2, and TCP/IP traffic. To save time and effort, install only the features needed for the technologies your users will be testing.

Important

If TN3270 at your site uses a separate address space from TCP/IP, LU2 testing features are required for capturing TN3270 traffic. Let your users know which testing features they should select to capture TN3270 traffic.

APPC APPLID definitions

APPC setup considerations

Log, Script, and Detail Data sets

For each APPC test script, the script create function generates three distinct types of information:

Conversation Log: Contains readable information showing recorded APPC conversations and scripts that contain APPC verbs issued by these conversations.
Script: Contains readable APPC verbs describing an entire APPC conversation. It also can contain binary data transmitted by the APPC verbs.
Detail Data: Contains binary data transmitted by the APPC verbs, if the data was not written into the script.

These three types of information can be written to as many as four PDSs. When creating a recording request using Global Recording ISPF screens, the user decides on data set and member names for the recorded data.

For example, all three types of information can be written to different members of a single PDS or to a different PDS, or some information can be written to a common PDS and other information to different PDSs.

You can preallocate data sets using ISPF’s standard Dataset Allocation screen (option 3.2). You can also write conversation logs, scripts, and detail data to a PDS with a record format of F, FB, V, or VB. The logical record length (LRECL) and block size (BLKSIZE) can be from 72 to 32760. The data set organization (DSORG) must be partitioned (PO) for script and detail data sets. The log data set can be either partitioned or sequential (PS). The amount of space necessary for these files depends on the amount of data recorded.

Important

You can create scripts automatically after data capture ends, or you can suspend script creation and create scripts manually using Review Repository.

Conversation Log

Script Create writes a set of six records to the log for each recorded APPC conversation. Collectively, these six records occupy approximately 800 bytes. To estimate log space requirements, multiply the number of conversations by 800.

To avoid horizontal scrolling when viewing 80-character log data sets, set the LRECL to 76 with an RECFM of VB.

Script

A script contains all APPC verbs from both sides of a single APPC conversation. Each APPC verb requires at least one record in the script; an APPC verb with many parameters can require several records. Each APPC verb occupies about 10 to 40 bytes on a script data set.

By default, Script Create writes a timestamp record for each APPC verb in the script. Users can also suppress timestamps when the script is created. Each timestamp record occupies approximately 35 bytes.

Script Create writes two 20-byte records every time the sender switches direction (gives control to the partner application). Use the following formulas as guides when estimating space requirements for scripts:

bytes-for-verbs = number-of-verbs x 40
bytes-for-timestamps = number-of-verbs x 35 (if timestamps are present)
bytes-for-switches = number-of-switches x 2 x 20
bytes-in-member = bytes-for-verbs + bytes-for-timestamps +
bytes-for-switchesTo browse or edit the script data set on an 80 character terminal without having to scroll horizontally, we recommend an LRECL of 76 with an RECFM of VB.

When users request a recording of APPC conversations, they can also request that detail data be placed in the script with the APPC verbs. This practice increases the space used for each member in the script data set. If detail data is retained like this, users must increase size values for the script by the size values for the detail data.

Detail data

Detail files contain binary data transmitted by several APPC verbs. See Script/Detail Dataset Options for suggestions on ways to store detail data. Detail data location does not affect playback efficiency.

The amount of detail data associated with an APPC verb varies considerably. If you know the average amount of data transmitted by the APPC application, use the following formula to determine this amount:

bytes-in-member = number-of-verbs-with-data x (average-data-per-verb + 12)To reduce overhead when accessing the detail file, we recommend a minimum LRECL of 1000 with a RECFM of VB.

Script/Detail dataset options

Users can place detail data into the same PDS member as the script, or into a different member or PDS separate from APPC verbs. Optionally, users can divide the detail data into separate members for outbound data (sent from the ALLOCATE sender to the ALLOCATE receiver) and inbound data (sent from the ALLOCATE receiver to the ALLOCATE sender).

Here are three ways to combine or separate scripts and detail data members in a single PDS or in multiple PDSs. For most users, we recommend option 1 or 2.

Option 1 puts APPC verbs and all detail data into a single PDS member. Use this option to see all of the data for a conversation in a single location.
Option 2 separates the APPC verbs from the detail data. The detail data is placed in a single member (both inbound and outbound data). Use this option to keep the script member separate from detail data.
Option 3 separates the APPC verbs from the detail data. The inbound and outbound detail data are stored in separate members of one or two PDSs. Use this option to view or manipulate inbound and outbound data separately.

APPC APPLID definitions for VTAM

Performance Test for Mainframe Servers requires a VTAM LU, defined as an APPL, to play back APPC conversations. Performance Test for Mainframe Servers can share one LU for all APPC conversations in a single unattended playback job. If your users will be running more than one job at a time, create an LU for each job. If your users connect to an IMS application program using the IMS LU6.1 adapter for LU6.2, you must define APPLs that do not have parallel session support.

Important

For successful playback, the virtual LUs must have the same characteristics as the APPC APPLID LUs that your application uses. As you complete the following installation instructions, make sure that you modify the provided samples accordingly. If your applications use different types of LUs, define LUs with unique prefixes for each type.

To create APPC APPLIDs:

Review the appropriate INSTALL member:
- APPC100 provides a sample APPC APPLID definition (APPC100 Sample APPC APPLID Definition).
- APPC150 provides a sample APPC APPLID definition for IMS LU6.1 (APPC150 Sample APPC APPLID Definition for the IMS LU6.1).
APPC100 Sample APPC APPLID Definition
*********************************************************************
*                                                                   *
* SAMPLE VTAM APPLICATION DEFINITIONS FOR PERFORMANCE TEST AND     *
* APPC.                                                            *
*                                                                   *
* PERFORMANCE TEST WILL USE THESE APPL STATEMENTS DURING PLAYBACK *
* OF APPC CONVERSATIONS. ONE APPL STATEMENT IS REQUIRED FOR       *
* EACH PERFORMANCE TEST PLAYBACK JOB THAT IS RUN SIMULTANEOUSLY    *
* WITH OTHER PERFORMANCE TEST PLAYBACK JOBS.                       *
*                                                                   *
* IF ONLY A SINGLE PERFORMANCE TEST PLAYBACK JOB IS RUN AT ANY ONE *
* TIME, ONLY A SINGLE APPL STATEMENT IS NEEDED.                    *
*                                                                   *
*********************************************************************
* @01 RVR 02/12/07 CN77041 REBRANDING                            *
* @02 DLP 12/21/22 ZENG-269862 REBRANDING                        *
*********************************************************************
HS620000 VBUILD TYPE=APPL
HS620001 APPL ACBNAME=HS620001,                                       X
               APPC=YES,                                               X
               ATNLOSS=ALL,                                            X
               AUTH=(ACQ,SPO),                                         X
               AUTOSES=0,                                              X
               DLOGMOD=#INTER,                                         X
               SECACPT=AVPV,     /* REMOVE IF VTAM 3.3 OR EARLIER */   X
               SYNCLVL=SYNCPT,   /* SET = CONFIRM IF NO SYNC USED */   X
               VERIFY=NONE,                                            X
               DSESLIM=256,EAS=256,PARSESS=YES,                        X
               SRBEXIT=NO
APPC150 Sample APPC APPLID Definition for the IMS LU6.1
*********************************************************************
*                                                                   *
* SAMPLE VTAM APPLICATION DEFINITIONS FOR PERFORMANCE TEST, APPC, *
* AND THE IMS LU6.1 ADAPTER.                                       *
*                                                                   *
* PERFORMANCE TEST WILL USE THESE APPL STATEMENTS DURING PLAYBACK *
* OF APPC CONVERSATIONS WITH THE IMS LU6.1 ADAPTER. ONE APPL      *
* STATEMENT IS REQUIRED FOR EACH CONVERSATION THAT IS RUN          *
* SIMULTANEOUSLY WITH OTHER CONVERSATIONS IN THE SAME OR OTHER     *
* PERFORMANCE TEST PLAYBACK JOBS.                                  *
*                                                                   *
* THE IMS LU6.1 ADAPTER DOES NOT ALLOW PARALLEL SESSIONS BETWEEN   *
* THE TRANSACTION PROGRAM (PERFORMANCE TEST) AND THE ADAPTER.      *
*                                                                   *
*********************************************************************
* @01 RVR 02/12/07 CN77041 REBRANDING                            *
* @02 DLP 12/21/22 ZENG-269862 REBRANDING                        *
*********************************************************************
HS620000 VBUILD TYPE=APPL
HS620001 APPL ACBNAME=HS620001,                                       X
               APPC=YES,                                               X
               ATNLOSS=ALL,                                            X
               AUTH=(ACQ,SPO),                                         X
               AUTOSES=0,                                              X
               DLOGMOD=#INTER,                                         X
               SECACPT=AVPV,     /* REMOVE IF VTAM 3.3 OR EARLIER */   X
               SYNCLVL=CONFIRM,                                        X
               VERIFY=NONE,                                            X
               DSESLIM=1,EAS=1,PARSESS=YES,                            X
               DMINWNL=0,DMINWNR=0,                                    X
               SRBEXIT=NO
To install the members as a major node, copy the members to SYS1.VTAMLST.
To install definitions as minor nodes, copy the APPL statements to an existing VTAM major node.
Warning
Important
We recommend setting up APPLIDs as major nodes.
If necessary, modify the definition to meet your requirements or add additional APPL statements.
Warning
Important
DLOGMOD, in both sample members, is set to the default IBM logmode. If your APPC applications use a different logmode, change the value of this parameter.
Ensure the virtual terminals are automatically activated at VTAM startup. If they are not, activate them manually by entering the following MVS operator command, where nodename is the member you created in SYS1.VTAMLST:
V NET,ACT,ID=nodename

APPC APPLID definitions for VTAM applications

Define APPC Logical Units to VTAM applications such as CICS. This section explains how to define APPC APPLIDs to CICS and IMS.

APPC APPLIDs for CICS

You must define APPC APPLIDs to CICS to use Performance Test for Mainframe Servers to play back CICS APPC conversations.

To define APPC APPLIDs to CICS:

Open INSTALL member APPC200.

APPC200 Sample CICS Definitions for Performance Test APPLIDs Adapter

***********************************************************************
*                                                                     *
* SAMPLE CICS DEFINITIONS FOR PERFORMANCE TEST APPLS.                *
*                                                                     *
* THESE DEFINITIONS ARE NEEDED BY CICS TO COMMUNICATE WITH           *
* PERFORMANCE TEST DURING PLAY BACK OF APPC CONVERSATIONS.           *
*                                                                     *
*                                                                     * 00140000
* CHANGE ACTIVIY - AS FOLLOWS:                                        * 00140000
*                                                                     * 00140000
* @01 JFC 08/23/02 - CHANGED CSDNAME ON SESSIONS PARM TO NAME=>PN34219* 00140000
* @02 RVR 02/12/07 CN77041 REBRANDING                              * 00140000
* @03 DLP 12/21/22 ZENG-269862 REBRANDING                        *
***********************************************************************
   DEFINE
     CONNECTION(name)        Internal CICS connection name
     GROUP(groupname)
     ACCESSMETHOD(VTAM)      Must be 'VTAM'
     PROTOCOL(APPC)          Must be 'APPC'
     SINGLESESS(N)           'N' is highly recommended, could be 'Y'
     NETNAME(name)           LU name for one of PERFORMANCE TEST's LUs
     AUTOCONNECT(NO)         Should be 'NO'

   DEFINE
      SESSIONS(name)
      GROUP(groupname)
      PROTOCOL(APPC)         Must be 'APPC'
      CONNECTION(name)       Set to the associated CONNECTION name
      MODENAME(name)         VTAM logon mode name for LU6.2
      MAXIMUM(m1,m2)         'm1' is maximum parallel sessions, must
                             be greater or equal to the maximum number
                             of simultaneous sessions PERFORMANCE TEST
                             will request during playback.
                             'm2' is the maximum number of contention
                             winners, must be greater or equal to the
                             maximum number of simultaneous contention
                             winners PERFORMANCE TEST will request
                             during playback.
      AUTOCONNECT(NO)        Should be 'NO'

2. Supply parameter values for the existing placeholder. Add a connection and sessions statement for each LU you defined to VTAM.

3. Use DFHCSDUP to install these definitions.

4. Make sure that the group name you supply is in a group list started by CICS.

LU0 and LU2 terminal definitions

Performance Test for Mainframe Servers supports capturing and playing back LU0 and LU2 traffic. If your site requires this functionality, define your LU devices to VTAM and your VTAM applications.

For more information, see:

For LU2 playback, see 3270 Terminal Definitions.
For LU0 playback, see LU0 Terminal Definitions.

TCP/IP considerations

Performance Test for Mainframe Servers offers TCP/IP capture capability.

TCP/IP setup considerations

Secured Sockets Layer (SSL) support

Support for capturing SSL data is provided for System SSL beginning with OS/390 V2R7.0. This is the standard application interface for SSL on the OS/390 platform. Optionally, support may also be added for the version of SSL used by WebSphere Application Server beginning with OS/390 V2R7.0. Secured Socket Layer (SSL) support is only available for HTTPS protocol. All other Secured Socket Layer (SSL) protocols are not currently supported.

If you need SSL support, specify parameter TCP_SSL=YES and put the correct modules in the LPA. If Performance Test does not find these modules, it will issue a warning message and continue without SSL support.

For System SSL, load the GSKSSL load module into the LPA. Add the GSKSSL module from SYS1.SIEALNKE into the LPA prior to starting the Global Recording started task, preferably at IPL time. Either:

Issue the SETPROG command:

SETPROG LPA,ADD,MOD=GSKSSL,DSNAME=SYS1.SIEALNKE

Issue the SET PROG=xx command using an ADD LPA directive in a PROGxx member in the SYS1.PARMLIB or your installation’s default PARMLIB:

LPA ADD MODNAME(GSKSSL) DSNAME(SYS1.SIEALNKE)

Use any tool that can dynamically add a module into the LPA as described in the previous options.

Warning

If any of your applications use the System SSL access module GSKSSL from a STEPLIB or JOBLIB, in effect bypassing the module GSKSSL in the LPA, Global Recording may not function properly for SSL.

Operating System facility preparations

If you are using SSL support, authorize the following two libraries:
- C++ run-time library (CEE.SCEERUN)
- Encryption function library (SYS1.SIEALNKE)
Before you can use SSL support, you need to create a key database and authorize it properly. Set this encryption key database explicitly for TCP/IP playbacks, for all users running playbacks with HTTPS connections will require access to the database. See IBM’s Cryptographic Services System Secure Sockets Layer Programming Manual for more information on setting up a key database. As you set up the database, note the full HFS path and database name, and the database password. This information is required for TCP/IP playback of HTTPS scripts.
Add in certificates. If your server is using “self-signed” certificates, or is using a certificate authority not in the list provided by GSKKYMAN, you should import a certificate from the server, or you can export the server certificate from your key database. See IBM’s Cryptographic Services System Secure Sockets Layer Programming Manual for more information.
If your site is using the UNIX System Services (USS) AUTOMOUNT for the HFS directories containing the encryption routines supplied with USS, you will need to add a USS segment to the security profile of each user who will be running HTTPS playbacks. See UNIX System Services Planning for more information.

Db2 connect configuration

Db2 Connect data encryption is time-sensitive and may cause playback to fail. To ensure successful playback, configure Db2 Connect security for SERVER Authentication and disable data encryption. Refer to your Db2 Connect documentation for more information.

TCP/IP Installation considerations

Review the Global Recording started task initialization parameters contained in the version of the HSCM PARMLIB member you are using. Modify as needed. Pay close attention to the values of the following parameters:

MAXIMUM_TCP_CONNECTIONS
OMVS_JOBNAME
TCP_SSL
TCP_MQ_ECSA_BUFFER_COUNT
TCP_MQ_ECSA_BUFFER_SIZE
TCPIP_JOBNAMES
MAXIMUM_CONCURRENT_TCP_MQ_CALLS
MAXIMUM_TCP_RECORD_SIZE.

Important

Global Recording Customization lists and defines all available parameters. Additionally, Started Task Initialization Parameters provides comprehensive instructions for modifying specific parameters to support the volume of traffic in your system.

The userIDs associated with the running of Global Record, playback, or reporting jobs that involve TCP/IP and/or Websphere MQ must be defined to the security system with a profile that includes an OMVS segment. Users submitting playback or reporting tasks that use Secure Sockets Layer (SSL or TLS) must have their own OMVS segment defined for their security profile, as the system-wide default OMVS segment is insufficient. An OMVS segment can be associated with an existing RACF user profile with the command:
ALTUSER userid OMVS(UID(uid_value))
The alternative method of creating a system-wide default OMVS segment (the RACF profile BPX.DEFAULT.USER) rather than individual user OMVS segments, is not sufficient if users will be performing playbacks that use the SSL feature. Users playing back HTTPS datastreams must have their own OMVS segment defined for their RACF profile.
Ensure that the TCP/IP script playback program (TCPPBMN) runs from an authorized library.
Customize JCL and Procedure Members. INSTALL members TCPRUN, TCPPLAY, and ESREPT1 contain JCL required to play back TCP/IP scripts and create reports. To ensure that playback and reporting run correctly, make the following changes based on your site-specific information:
1. TCPRUN
  INSTALL member TCPPLAY contains a JCL procedure. You may want to move this member to a JCL procedure library. If you do this, modify the UPROCS statement in TCPRUN.
2. TCPPLAY
  1. Make sure LIBPRFX points to the high-level qualifier for the CEE/C+ libraries.
  2. Make sure the SET LOAD statement points to the Performance Test load library at your installation.
  3. Create a fixed block sequential data set containing the following records:
    Record 1 — The fully qualified key database name. For example, if you created a key database name key.kdb in HFS directory u/hper/user1, the first record in the SSLINFO data set would be:
    /u/hper/user1/key.kdb
    Record 2 — The key database password. For example, if you created a key database name key.kdb with the password of hper, the second record in the SSLINFO data set would be:
    hper
    Record 3 — A string reserved for future use. The third record in the SSLINFO data set should be:
    QAH
  4. In the TCPPLAY proc, typically located in INSTALL, update the SSLINFO DD statement to point to the data set created in the previous step.
  5. Optionally, you can copy this JCL procedure to another proclib. If you do, be sure to modify the JCL TCPRUN (UPROCS) to point to the other proclib.
3. ESREPT1
  Make sure 'SET LOAD', points to the Performance Test load library (SQQFLOAD).
Set up playback and reporting asset libraries and populate them with members containing sample JCL and playback and reporting statements. These libraries are necessary to use some of the samples.
1. Open member ESPBCOPY found in the Performance Test INSTALL library.
2. On 'SET SAMP =', specify the fully qualified data set name of the Performance Test samples library (SQQFSAMP).
3. On 'SET REPT=', specify a data set name for the reporting asset library being created.
4. On 'SET DISK=', specify the DASD esoteric (unit name) to be used.
5. Submit the Job.
Configure Db2 Connect security for SERVER Authentication without encryption. This task must be performed for every instance of Db2 Connect you intend to capture.

Offset and Length determination macros

Performance Test provides REXX macros to aid users with determining offset and length values for data-replacement logic.

To make these macros available, copy the following SQQFEXEC members into a library in each user’s SYSPROC DD concatenation:

LOCPOS
BRULE
BRULES.

Performance Test for Mainframe Servers customization

Performance Test for Mainframe Servers Primary Option Menu

You can alter the short and long names and the title on the Performance Test for Mainframe Servers Primary Option Menu by editing sample library data set ETRM@xxx (where xxx is the 3-character value from the PRIMARY_OPTION_MENU_LANGUAGE= parameter on the $PNLOPT TYPE=ENTRY macro), then reassembling.

The ETRM@xxx source consist of a series of $PNLOPT macros. To alter the title, short name, and/or long name, change the text after the following keywords:
- TITLE = (maximum characters: 80)
- STEXT =(maximum characters: 25)
- LTEXT =(maximum characters: 50).
Reassemble and link-edit ETRM@xxx. Sample JCL is in INSTALL member ASSEMPNL.

MAPD program macro

MAPD is a program macro that allows the user to map TCP/IP message data from a script or detail data set into File-AID/MVS to review or edit in a formatted context.

Important

This feature requires a supported version of File-AID/MVS. See the Performance Test Release Notes for supported versions of File-AID.

This feature is also available for WebSphere MQ testing with Performance Test for WebSphere MQ. If you are installing both Performance Test for Mainframe Servers and Performance Test for WebSphere MQ, you need to perform these procedures only once.

To enable MAPD:

Concatenate the Performance Test load library to ISPLLIB (ISPF load library DD statement).
Concatenate the Performance Test panel library to ISPPLIB (ISPF panel library DD statement).
Concatenate the Performance Test message library to ISPMLIB (ISPF message library DD statement).
Concatenate the File-AID/MVS load library to ISPLLIB (ISPF load library DD statement).
Concatenate the File-AID/MVS panel library to ISPPLIB (ISPF panel library DD statement).
Concatenate the File-AID/MVS message library to ISPMLIB (ISPF message library DD statement).
Concatenate the File-AID/MVS CLIST library to the TSO SYSPROC library (TSO system procedure library).

For more information about ISPF edit macros, consult IBM’s ISPF Edit and Edit Macros.

Specialized 3270 and APPC recording methods

Performance Test for Mainframe Servers offers the ability to record the activity of specified users. This feature is automatically enabled for APPC capture. If your site also requires this feature for 3270 capture, see Specialized 3270 Recording Methods.

Number of APPC APPLIDs

If you need to change the number of APPC APPLIDs, be sure to modify the APPLIDs in both VTAM and your VTAM applications. Refer to APPC APPLID Definitions for VTAM, and APPC APPLID Definitions for VTAM Applications.

Prefix of your APPC APPLIDs

If you change the prefix of the Performance Test APPLIDs (for example, HS620001 to CUST0001), make corresponding modifications to the CICS LU6.2 terminal definitions.

Important

For unattended playback batch jobs, add LU62PFX(cccc) to the CONTROL statement, where cccc is the new prefix. The default prefix is HS62.
The prefix and suffix together cannot exceed eight bytes.

Suffix of your APPC APPLIDs

If you change the suffix length of the Performance Test APPLIDs (for example, HS620001 to HS62001), make corresponding modifications to the CICS LU6.2 terminal definitions.

Important

For unattended playback batch jobs, add LU62SFX(n) to the CONTROL statement, where n is the new suffix. Default suffix length is four.
The length of the suffix has a direct impact on the number of logical units that can be defined. For example, suffix=2 implies a maximum of 99 logical units.
The prefix and suffix together cannot exceed eight bytes.

Reporting asset library

These steps create a reporting assets library and populate it with members containing sample reporting statements and JCL.

Open member ESPBCOPY found in the Performance Test INSTALL library.
On 'SET SAMP =', specify the fully qualified data set name of the Performance Test samples library (SQQFSAMP).
On 'SET REPT=', specify a data set name for the reporting asset library being created.
On 'SET DISK=', specify the DASD esoteric (unit name) to be used.
Submit the Job.

Performance Test for WebSphere MQ

Performance Test for WebSphere MQ configuration

Review the Global Recording started task initialization parameters contained in your HSCM PARMLIB member. Modify as needed. Pay close attention to the values of the following parameters:
- MQ_QUEUE_MANAGER_NAME
- MAXIMUM_MQ_CONNECTIONS
- TCP_MQ_ECSA_BUFFER_SIZE
- TCP_MQ_ECSA_BUFFER_COUNT
- MAXIMUM_CONCURRENT_TCP_MQ_CALLS.
Warning
Important
Some parameters are not listed because they have default values that support most systems. Global Recording Customization lists and defines all available parameters. See Started Task Initialization Parameters for comprehensive instructions for modifying specific parameters to support the volume of traffic in your system.
The userIDs associated with the running of Global Record, playback, or reporting jobs that involve TCP/IP and/or Websphere MQ must be defined to the security system with a profile that includes an OMVS segment. Users submitting playback, or reporting tasks that use Secure Socket Layer (SSL or TLS) must have their own OMVS segment defined for their security profile, as the system-wide default OMVS segment is insufficient. An OMVS segment can be associated with an existing RACF user profile with the command:
ALTUSER userid OMVS(UID(uid_value))
The alternative method of creating a system-wide default OMVS segment (the RACF profile BPX.DEFAULT.USER) rather than individual user OMVS segments is permitted. However, if Performance Test for Mainframe Servers is or will be installed, and users will be performing playbacks that use the SSL feature, the users must have their own OMVS segment defined for their RACF profile in order to play back the HTTPS datastreams.
Ensure that the WebSphere MQ script playback program (TCPPBMN) runs from an authorized library.
Set up playback and reporting control libraries and populate them with members containing sample JCL and playback and reporting statements. These libraries are necessary for successful playback and report generation.
1. Open member MQPBCOPY found in the Performance Test INSTALL library.
2. On 'SET LOAD=', specify the fully qualified data set name of the Performance Test load library (SQQFLOAD).
3. On 'SET SAMP =', specify the fully qualified data set name of the Performance Test samples library (SQQFSAMP).
4. On 'SET CNTL=', specify a fully qualified data set name for the playback control library being created.
5. On 'SET REPT=', specify a fully qualified data set name for the reporting control library being created.
6. On 'SET REPO=’ specify a fully qualified data set name for the sample capture repositories. The name you specify will be appended with an integer for each repository being copied.
7. On 'SET DISK=', specify the DASD esoteric (unit name) to be used.
8. Submit the Job.
Set up JCL and Procedure Libraries. INSTALL members MQRUN, MQPLAY, MQRUN1, MQPLAY1, and MQREPT1 contain JCL required to play back WebSphere MQ scripts and create reports. To ensure that the unattended playback and reporting run correctly, make the following changes based on your site-specific information:
1. MQRUN
  INSTALL member MQPLAY contains a JCL procedure. If you move this member to a procedure library, modify the UPROCS statement in MQRUN.
2. MQPLAY
  1. Make sure LIBPRFX points to the high-level qualifier of your CEE (C++) libraries.
  2. Make sure 'SET LOAD' points to the Performance Test load library.
  3. If your MQ SCSQAUTH and SCSQLOAD libraries are not in the link list or LPA, concatenate these libraries to the STEPLIB DD.
3. MQRUN1
  1. Create a job card.
  2. On 'SET CNTLDS', specify the playback control library name you provided in Step 4.
  3. On 'SET REPTDS', specify the reporting control library name you provided in Step 4.
4. MQPLAY1
  1. On 'SET LIBPRFX', specify the high-level qualifier of your CEE/C+ libraries.
  2. Make sure 'SET LOAD', points to the Performance Test load library (SQQFLOAD).
  3. If your MQ SCSQAUTH and SCSQLOAD libraries are not in the link list or LPA, concatenate these libraries to the STEPLIB DD.
5. MQREPT1
  1. On 'SET LIBPRFX', specify the high-level qualifier of your CEE/C+ libraries.
  2. Make sure 'SET LOAD', points to the Performance Test load library.
Modify the following parameters in the HSCM PARMLIB member to support generation of the log file used to run playback and reporting jobs.
1. PRODUCT_SAMPLES: Specify the name of library containing playback and reporting procedures such as MQPLAY and MQRUN. These procedures reside in the Performance Test INSTALL library by default.
2. HIPERSTATION_PLAYBACK_CONTROL: Specify the name of playback control library created in Step 4.
3. HIPERSTATION_REPORT_CONTROL: Specify the name of the reporting control library created in Step 4.
The following parameters specify space allocation for the temporary CSV dataset that Performance Test creates while generating an HTML Event Summary:
1. TEMPORARY_UNIT: Specify the DASD unit name to contain the temporary data set. SYSDA is the default. This field is required.
2. TEMPORARY_VOLUME: Specify the volume to contain the temporary data set. This field is optional.
3. TEMPORARY_SPACE_UNITS: Specify the allocation space units. Valid values are CYLS (cylinders), TRKS (tracks), or BLKS (blocks). CYLS is the default. This field is required.
4. TEMPORARY_PRIMARY_ALLOCATION: Specify the initial number of space units to allocate for the temporary data set. 7 is the default. This field is required.
5. TEMPORARY_SECONDARY_ALLOCATION: Specify the number of additional space units to allocate if the temporary data set requires more space. 3 is the default. This field is required.
6. TEMPORARY_MANAGEMENT_CLASS: Specify the SMS Management Class. This field is optional.
7. TEMPORARY_STORAGE_CLASS: Specify the SMS Storage Class. This field is optional.
8. TEMPORARY_DATA_CLASS: Specify the SMS Data Class. This field is optional.
Optionally, enable offset and length determination macros. These macros aid users with determining offset and length values for data-replacement logic. Copy SQQFEXEC members LOCPOS, BRULE, and BRULES into a library that is in each user’s SYSPROC DD concatenation.

Important

If you enabled these macros during Performance Test for Mainframe Servers installation, you have already completed this step.

Performance Test for WebSphere MQ Customization

Performance Test for WebSphere MQ primary option menu

You can alter the short and long names and the title on the Performance Test for WebSphere MQ Primary Option Menu by editing sample library data set ETRM@xxx (where xxx is the 3-character value from the PRIMARY_OPTION_MENU_LANGUAGE= parameter on the $PNLOPT TYPE=ENTRY macro), then reassembling.

The ETRM@xxx source consist of a series of $PNLOPT macros. To alter the title, short name, and/or long name, change the text after the following keywords:
- TITLE = (maximum characters: 80)
- STEXT =(maximum characters: 25)
- LTEXT =(maximum characters: 50).
Reassemble and link-edit ETRM@xxx. Sample JCL is in INSTALL member ASSEMPNL.

MAPD program macro (Optional)

MAPD is an program macro that allows the user to map MQ message data from a script or detail data set into File-AID/MVS to review or edit in a formatted context.

Important

This feature requires a supported version of File-AID/MVS.

This feature is also available for TCP/IP testing with Performance Test for Mainframe Servers. If you have already completed this procedure during Performance Test for Mainframe Servers installation, skip this section.

To enable MAPD:

Concatenate the Performance Test load library to ISPLLIB (ISPF load library DD statement).
Concatenate the Performance Test panel library to ISPPLIB (ISPF panel library DD statement).
Concatenate the Performance Test message library to ISPMLIB (ISPF message library DD statement).
Concatenate the File-AID/MVS load library to ISPLLIB (ISPF load library DD statement).
Concatenate the File-AID/MVS panel library to ISPPLIB (ISPF panel library DD statement).
Concatenate the File-AID/MVS message library to ISPMLIB (ISPF message library DD statement).
Concatenate the File-AID/MVS CLIST library to the TSO SYSPROC library (TSO system procedure library).

For more information about ISPF edit macros, consult IBM’s ISPF Edit and Edit Macros.

Reporting asset library

These steps create a reporting assets library and populate it with members containing sample reporting statements and JCL.

Open member MQPBCOPY found in the Performance Test INSTALL library.
On 'SET SAMP =', specify the fully qualified data set name of the Performance Test samples library (SQQFSAMP).
On 'SET REPT=', specify a data set name for the reporting asset library being created.
On 'SET DISK=', specify the DASD esoteric (unit name) to be used.

Submit the Job.