Guided Configuration Field Definitions

Install Performance Test for VTAM screens

This section defines the fields on the Performance Test for VTAM installation screens:

Establish access to the product suite screen

The Guided Configuration uses the LIBDEF utility to set up the ISPF environment. After you complete the following fields and press Enter, the Guided Configuration creates the CLIST member and copies it into specified CLIST library.

Performance Test CLIST name

The name of a member to contain the Performance Test CLIST. The Guided Configuration creates this member. The default value is LIBDEF.

CLIST library

The CLIST library in your user’s TSO SYSPROC concatenation into which the Performance Test CLIST can be placed. The default value is the install library from which Guided Configuration was executed.

Create Global Recording request file screen

Performance Testrequires a data set to track information from the Global Recording feature. Global Recording uses this data set to store recording request records and include/exclude lists.

Complete all of the fields on this screen, then type G on the Command line and press Enter to create the data set.

GRREQ DSN

A name for the request data set. Enter a valid data set name up to 38 characters. This field defaults to a DSN that starts with your TSO user ID and the Performance Test build number and ends with GRREQ.

The number of cylinders to allocate for the file. This field’s default value is 5.

Secondary allocation

The number of additional cylinders to allocate if the primary allocation is exceeded. The default value is 1.

Volumes

The serial number of the volume on which to store the request data set. This field is optional, and it accepts up to six alphanumeric characters.

Install Global Record started task

Global recording is accomplished through the use of an MVS started task. After you complete the fields and press Enter, the Guided Configuration prepares the started task JCL and copies it into the specified procedure library.

The system procedure library in which to place the started task JCL. This field defaults to SYS1.PROCLIB.

Task name

A name for the member that will contain the Global Recording started task JCL. This field defaults to GRTASK.

Install Repository Registry started task screen

Repository Registry is accomplished through the use of an MVS started task. After you complete the following fields and press Enter, the Guided Configuration prepares the started task JCL and copies it into the specified procedure library.

The Archive Repository Registry procedure will be copied to the specified system procedure library if it differs from your Installation library. The JCL to execute the Archive Repository Registry procedure will be created in the Installation library with a member name of HSREGEN.

Defines the location where the Archive Repository Registry installation procedure will be stored. This field defaults to the install library from which the Guided Configuration is running.

Repository Procedure Member name

Defines the Archive Repository Registry Started Task Member name.

Install auto-start script create started task

3270 and APPC Global Recording requests automatically initiate script creation when recording finishes unless the user selects an option to suspend script creation. Global Recording initiates script creation by issuing an MVS start command for the 3270/APPC auto-start script create JCL. After you complete the following fields and press Enter, the Guided Configuration prepares the JCL and copies it to the specified system procedure library.

System procedure library

The system procedure library in which to place the auto-start script create JCL. This field defaults to the install library from which the Guided Configuration is running.

VTAM auto-start script create started task procedure name

The name for the member that will contain the auto-start script create JCL. This field defaults to HSSCREAT and corresponds to the Global Recording parameter SCRIPT_CREATE_TASK.

VTAM Global Recording parameters screen

Global Recording stores captured information in global capture buffers. The size and number of global capture buffers, along with a few other parameters, impact how often the buffers are flushed and processed, which impacts both Global Recording and system performance. Buffer settings that are too high or too low for the volume of traffic in your system, may result in delayed recording request monitoring information, error messages, or even lost data due to slow processing or insufficient common storage.

Before completing the fields on this screen, determine the typical and peak volume, in kilobytes, of 3270, LU0, and APPC data that flows through your system.

The following fields prompt you for Global Recording parameter values. To modify these values after initial installation, update and refresh the HSCM PARMLIB member.

Number of VTAM recording buffers

The number of buffers to use for recording 3270, LU0, and APPC traffic. Enter a number between 2 and 255. Set the buffer count high enough to accommodate peak volume. To determine the number of buffers required, multiply the peak-to-typical volume ratio by three or four. For example, if peak volume is 450K per second and typical volume is 150K per second (a ratio of 3:1), set the buffer count between 9 and 12.

This field corresponds to the ECSA_BUFFER_COUNT parameter.

Size of VTAM recording buffers in kilobytes

The size, in kilobytes, of each global capture buffer used to record 3270, LU0, and APPC traffic. Enter a number between 32K and 1024K. Global Recording typically flushes and processes the buffers as they fill. For optimum performance, Global Recording needs to flush and process one to two buffers per second. Use your typical data flow to determine the buffer size required for optimum performance. For example, if your typical data flow is 150K per second, set buffer size between 75K and 150K.

This field corresponds to the ECSA_BUFFER_SIZE parameter.

Maximum number of active VTAM LU-LU sessions

The maximum number of VTAM LU-to-LU sessions expected at any one time on the MVS system on which you are installing Performance Test. Enter a numeric value between 0 and 65,535. Upon startup, Global Recording creates information tracking tables in ECSA storage based on the specified maximum number of logon/logoff events and maximum VTAM LU-to-LU sessions. If the actual counts are higher that these values, Global Recording has to allocate additional ECSA storage. While processing ECSA allocations, Global Recording may fall behind in processing captured traffic, which can produce error messages and compromise performance. Enter an accurate value to minimize CPU usage, eliminate unneeded data movement, and ensure optimum Global Recording and system performance.

Prohibit capture of LU0 traffic (Y/N)?

The flag to prohibit capture of LU0 traffic. Enter Y for yes or N for no. If LU0 support is unnecessary, reduce CPU utilization and improve Global Recording performance by entering Y in this field.

This field correspond to the ENABLE_LU0 parameter.

Allow capture by USERID (Y/N)?

The Global Recording by User ID flag. Global Recording supports the ability to record specified terminals and applications. To add the ability to capture 3270, LU0, or APPC activity based on user ID, enter Y in this field. Otherwise, enter N.

Security System (RACF, ACF2, TOPSEC)

The external security package that your site uses. Enter RACF, ACF2, or TOPSEC.

This field corresponds to the EXTERNAL_SECURITY_PRODUCT parameter.

Define virtual terminals screen

Performance Testrequires terminal definitions for the Domain Traveler and Unattended Playback features. It supports both alphanumeric and double-byte character set (DBCS) terminals.

The Define Virtual Terminals screen presents three options:

1. Alphanumeric
2. Double-byte character set
3. Both.

The selection field defaults to option 1 Alphanumeric. Type the applicable option number and press Enter to continue.

The Guided Configuration builds custom samples based on the values you supply on the terminal definition screens. It also generates instructions in the manual task lists that explain what to do with the custom samples.

If you need to add or modify terminal definitions after installation, return to this installation task. Update the appropriate fields. Finally, generate a manual task list and complete any new tasks.

After filling in all of the fields on this screen, type G on the Command line and press Enter to create the terminal definition sample. If you plan to run Performance Test on multiple MVS systems, create definitions for each system. When all of the necessary samples are created, press End to continue to the next installation screen.

MVS SYSID for these terminal definitions

The ID of the MVS system to associate with the terminal definitions. Performance Test selects the appropriate terminals to use for playback based on the ID for the MVS system on which Performance Test is running. DFLT is the default. If there are no terminal definitions associated with the current MVS system, Performance Test uses the definitions associated with DFLT.

Terminal name prefix (1 to 7 Characters)

A prefix, up to seven alphanumeric characters, to apply to the terminal names. The terminal name prefix plus the length of the terminal name suffix must equal eight or fewer characters.

Terminal name suffix length

Supply a value between 1 and 7 that in combination with the terminal name prefix equals eight or fewer characters. For example, if the terminal prefix is MVSA, the suffix length can be 4, 3, 2, or 1.

Number of terminals to define

Supply a value between 1 and 9999.

DLOGMODE (DEFAULT to use system default)

The name of the logon mode to apply to the terminal definitions. Either:

• Enter the name of an existing logon mode. This value must correspond to an entry in the default IBM logon mode table or to an entry in the table specified in the next field (MODETAB).
• Enter DEFAULT to omit the DLOGMODE parameter from the terminal definitions, which causes VTAM to select the appropriate value based on system settings.

This field holds up to 8 alphanumeric characters and defaults to DEFAULT.

MODETAB (DEFAULT to use system default)

The name of the logon mode table to apply to the terminal definitions. Either:

• Enter the name of the logon mode table that contains the entry specified in the DLOGMODE field.
• Enter DEFAULT to omit the MODETAB parameter from the terminal definitions, which causes VTAM to select the appropriate value based on system settings.

This field holds up to 8 alphanumeric characters and defaults to DEFAULT.

Define LU Type 2 DBCS virtual terminals screen

Complete all of the fields on this screen, then type G on the Command line and press Enter to create the terminal definition sample. If you plan to run Performance Test on multiple MVS systems, create definitions for each system. When all of the necessary samples are created, press End to continue to the next installation screen.

MVS SYSID for these terminal definitions

The ID of the MVS system to which the terminal definitions shall be assigned. Performance Test selects the appropriate terminals to use for playback based on the ID for the MVS system on which Performance Test is running. This field defaults to DFLT.

Terminal name prefix (1 to 7 characters)

A prefix, up to seven alphanumeric characters, to apply to the terminal names. The terminal name prefix plus the length of the terminal name suffix must equal eight or fewer characters.

Terminal name suffix length

A length for the terminal name suffix. Supply a value between 1 and 7 that in combination with the terminal name prefix equals eight or fewer characters. For example, if the terminal prefix is MVSA, the suffix length can be 4, 3, 2, or 1.

Number of terminals to define

The number of terminals to define. Supply a value between 1 and 9999.

DLOGMODE (DEFAULT to use system default)

The name of the logon mode to apply to the terminal definitions. Either:

• Enter the name of an existing logon mode. This value must correspond to an entry in the default IBM logon mode table or to an entry in the table specified in the next field (MODETAB).
• Enter DEFAULT to omit the DLOGMODE parameter from the terminal definitions, which causes VTAM to select the appropriate value based on system settings.

This field holds up to eight alphanumeric characters and defaults to DEFAULT.

MODETAB (DEFAULT to use system default)

The name of the logon mode table to apply to the terminal definitions. Either:

• Enter the name of the logon mode table that contains the entry specified in the DLOGMODE field.
• Enter DEFAULT to omit the MODETAB parameter from the terminal definitions, which causes VTAM to select the appropriate value based on system settings.

This field holds up to 8 alphanumeric characters and defaults to DEFAULT.

Define LU Type 0 Virtual Terminals Screen

Complete all of the fields on this screen, then type G on the Command line and press Enter to create the terminal definition sample. When all of the necessary samples are created, press End to continue to the next installation screen.

Terminal name prefix (1 to 7 characters)

A prefix, up to seven alphanumeric characters, to apply to the terminal names. The terminal name prefix plus the length of the terminal name suffix must equal eight or fewer characters.

Terminal name suffix length

A length for the terminal name suffix. Supply a value between 1 and 7 that in combination with the terminal name prefix equals eight or fewer characters. For example, if the terminal prefix is MVSA, the suffix length can be 4, 3, 2, or 1.

Number of terminals to define

The number of terminals to define. Supply a value between 1 and 9999.

DLOGMODE (DEFAULT to use system default)

The name of the logon mode to apply to the terminal definitions. Either:

• Enter the name of an existing logon mode. This value must correspond to an entry in the default IBM logon mode table or to an entry in the table specified in the next field (MODETAB).
• Enter DEFAULT to omit the DLOGMODE parameter from the terminal definitions, which causes VTAM to select the appropriate value based on system settings.

This field holds up to 8 alphanumeric characters and defaults to DEFAULT.

MODETAB (DEFAULT to use system default)

The name of the logon mode table to apply to the terminal definitions. Either:

• Enter the name of the logon mode table that contains the entry specified in the DLOGMODE field.
• Enter DEFAULT to omit the MODETAB parameter from the terminal definitions, which causes VTAM to select the appropriate value based on system settings.

This field holds up to 8 alphanumeric characters and defaults to DEFAULT.

Set up reporting asset library for VTAM screen

Performance Testreports are generated with batch jobs. Set up one or more system-level reporting asset libraries to store members containing sample JCL and SYSIN parameters. Populate the libraries with reporting assets that are tailored for your users. For example, create sample jobs for different types of reports or for different groups.

To create a library, complete all of the fields on this screen, type G on the Command line, and press Enter. When you have finished creating libraries, press End to continue to the next installation screen.

Report file DSN

The name of the reporting asset library. Either accept the default or enter a data set name. This field holds up to 44 characters. It defaults to a data set name that begins with the high-level qualifier that you specified earlier, followed by HS.REPORT.

DASD esoteric unit

The device on which to store the library. This field defaults to SYSDA.

Enable ISPF edit macros screen

Complete the field and press Enter. The Guided Configuration copies the appropriate procedures in the specified procedure library and continues to the next installation screen.

User procedure library

The procedure library to contain SPASTE and SPASTEX procedures. These procedures enable the ability to copy screen images from the Domain Traveler and Session Demo features and paste them into an ISPF edit session. Specify a library in the user’s TSO SYSPROC concatenation.

Web-based reporting screen

Fill in the Web Directory field, type G on the Command line, and press Enter. The Guided Configuration creates the web directory and its subdirectories. It populates each subdirectory with assets required by the web-based reporting feature. Press End to continue with the next installation screen.

Web Directory

The OMVS directory to contain JavaScript, images, REXX, and other web elements used by the web-based reporting feature. This field defaults to the value that you supplied when you built the SMP/E environment. This value must begin with a forward slash (/), it can be up to 39 characters, and it cannot contain spaces. Mixed case entries are preserved.

External security interface settings screen

Complete the fields on this screen and press Enter to continue to the next installation screen.

Security class name

The security, or resource, class name. The class name can be one to eight alphanumeric characters. For a list of resource classes, refer to IBM’s RACF Macros and Interfaces. The default value, NOSECURITY, disables function-access security.

Security entity name

The security entity name, which can be one to eight alphanumeric characters. This is the high-level qualifier for the resource names that Performance Test checks. For example, if a user attempts to access the Domain Traveler function, and you have accepted the default value of HIPER, Performance Test checks HIPER.FN.TESTING.

This field corresponds to the SECURITY_CLASS_ENTITY parameter.

Security volume ID

The volume ID that Performance Test specifies on the call to the security package when the class name is set to DATASET. This field holds up to six alphanumeric characters. The default value is HIPERX.

Install search on switch started task

Enter the appropriate system procedure library and procedure member name to create the Search on Switch Started Task. Press Enter to create the Search on Switch procedure and execution JCL, or Cancel to exit.

Defines the location where the Search on Switch procedure will be stored.

Search on Switch procedure member name

Defines the Search on Switch Started Task Member name.

Install Site Profile data set

The Site Profile data set will be used to store User Profile members. All users must have write access to this data set. For detailed information on setting up your user profiles, see Performance Test User Profiles.

Site Profile DSN

Specifies the name of the site profile data set.

Set up ATV manager

The Performance Test Automated Test Vehicle functionality provides a tool to build, deploy and manage testing vehicles, which will automate the regression and performance testing setup process. The Automated Test vehicle also automates the maintenance process to upgrade regression and performance test vehicles due to changes in the application environment. For complete information on how to use the ATV Manager, see the Performance Test Automated-Testing-Vehicle-ATV-Manager-User-Guide.

ATV Master Index DSN

Defines the Automated Test Vehicle Master Index File. This is a KSDS file used as an index for ATVs that are created. All user of the ATV Manager need READ access to this data set. Users creating Vehicles will need CONTROL access.

ATV High Level Qualifier

The Automated Test Vehicle HLQ is used as the High Level Qualifiers followed by the Vehicle name for data sets created by the ATV Manager. Users need ALTER access for these data set in order to use the ATV Manager.

Enter the appropriate JES node, SMTP Procedure name, and Job class to establish the E-mail interface to the Performance Test product. Press Enter to store the data and continue or Cancel to exit. For complete details on how to set up the HCI for Performance Test/Eclipse, see the BMC AMI Enterprise Common Components installation and configuration guide.

JES Node name

Specifies the JES node name to be used for SMTP E-mail services.

SMTP Procedure name

Specifies the Procedure name to be used for the SMTP E-mail services.

SMTP Job Class

Specifies the Job Class to be used for the SMTP E-mail services. This can be located in your site’s SMTP procedure under the ddname CONFIG.

Configure SIEM Data Delivery

Performance Testfor VTAM can be configured to deliver Security Incident and Event Management (SIEM) data to analytics and reporting tools, such as Splunk^®.

2. (Optional) Performance Test’s SIEM support also allows for optionally calling an exit program. See SIEM Exit Program for more information on creating an SIEM exit.
   • If an exit has been written, specify the name in the Program name field under Specify SIEM data exit program settings.
   • Specify whether XML validation should be performed. When the XML Validation option is set to Y, the XML is validated after the exit call to make sure it is still valid. The Y option is only valid when the SIEM destination is TCP and should only be used when testing the performance of an exit program. The default is N.

Install Performance Test for Mainframe Servers screens

This section defines the fields on the Performance Test for Mainframe Servers installation screens.

Establish access to the Product Suite screen

The Guided Configuration uses the LIBDEF utility to set up the ISPF environment. After you complete the following fields and press Enter, the Guided Configuration creates the CLIST member and copies it into the specified CLIST library.

Performance Test CLIST Name

The name of a member to contain the Performance Test CLIST. The Guided Configuration creates this member. The default value is LIBDEF.

CLIST Library

The CLIST library in your user’s TSO SYSPROC concatenation into which the Performance Test CLIST can be placed. The default value is the install library from which Guided Configuration was executed.

Create Global Recording request file screen

Performance Testrequires a data set to track information from the Global Recording feature. Global Recording uses this data set to store recording request records and include/exclude lists.

Complete all of the fields on this screen, type G on the Command line, and press Enter to create the data set. If you plan to run Performance Test on multiple MVS systems that share DASD, create a data set for each system. When all of the necessary data sets are created, press End to continue to the next installation screen.

GRREQ DSN

A name for the request data set. Enter a valid data set name up to 38 characters. This field defaults to a DSN that starts with your TSO user ID and the Performance Test build number, and ends with GRREQ.

The number of cylinders to allocate for the file. This field’s default value is 5.

Secondary allocation

The number of additional cylinders to allocate if the primary allocation is exceeded. The default value is 1.

Volumes

The serial number of the volume on which to store the request data set. This field accepts up to six alphanumeric characters.

Install Global Recording Started Task

Global recording is accomplished through the use of an MVS started task. After you complete the following fields and press Enter, the Guided Configuration prepares the started task JCL and copies it into the specified procedure library.

The system procedure library in which to place the started task JCL. This field defaults to the install library from which the Guided Configuration is running.

Task name

A name for the member that will contain the Global Recording started task JCL. This field defaults to GRTASK.

Install Auto-Start Script Create Started Task

3270 and APPC Global Recording requests automatically initiate script creation when recording finishes, unless the user selects an option to suspend script creation. Global Recording initiates script creation by executing a JCL procedure. After you complete the following fields and press Enter, the Guided Configuration prepares the JCL and copies it to the specified system procedure library.

System procedure library

The system procedure library in which to place the auto-start script create JCL. This field defaults to the install library from which the Guided Configuration is running.

VTAM Auto-start script create started task procedure name

A name for the member that will contain the auto-start script create JCL. This field defaults to HSSCREAT.

VTAM Global Recording parameters screen

Global Recording stores captured information in global capture buffers. The size and number of global capture buffers, along with a few other parameters, impact how often the buffers are flushed and processed, which impacts both Global Recording and system performance. Buffer settings that are too high or too low for the volume of traffic in your system may result in delayed recording request monitoring information, error messages, or even lost data due to slow processing or insufficient common storage.

Before completing the fields on this screen, determine the typical and peak volume, in kilobytes, of 3270, LU0, and APPC data that flows through your system.

Number of VTAM Recording Buffers

The number of buffers to use for recording 3270, LU0, and APPC traffic. Enter a number between 2 and 255. Set the buffer count high enough to accommodate peak volume. To determine the number of buffers required, multiply the peak-to-typical volume ratio by three or four. For example, if peak volume is 450K per second and typical volume is 150K per second (a ratio of 3:1), set the buffer count between 9 and 12.

This field corresponds to the ECSA_BUFFER_COUNT parameter.

Size of VTAM recording buffers

The size, in kilobytes, of each global capture buffer used to record 3270, LU0, and APPC traffic. Enter a number between 32K and 1024K. Global Recording typically flushes and processes the buffers as they fill. For optimum performance, Global Recording needs to flush and process one to two buffers per second. Use your typical data flow to determine the buffer size required for optimum performance. For example, if your typical data flow is 150K per second, set buffer size between 75K and 150K.

This field corresponds to the ECSA_BUFFER_SIZE parameter.

Maximum number of active VTAM LU-LU sessions

The maximum number of VTAM LU-to-LU sessions expected at any one time on the MVS system on which you are installing Performance Test. Enter a numeric value between 0 and 65,535. Upon startup, Global Recording creates information tracking tables in ECSA storage based on the specified maximum number of logon/logoff events and maximum VTAM LU-to-LU sessions. If the actual counts are higher that these values, Global Recording has to allocate additional ECSA storage. While processing ECSA allocations, Global Recording may fall behind in processing captured traffic, which can produce error messages and compromise performance. Enter an accurate value to minimize CPU usage, eliminate unneeded data movement, and ensure optimum Global Recording and system performance.

Prohibit Capture of LU0 Traffic

The flag to prohibit capture of LU0 traffic. Enter Y for yes or N for no. If LU0 support is unnecessary, reduce CPU utilization and improve Global Recording performance by entering Y in this field.

This field correspond to the ENABLE_LU0 parameter.

Security System

The external security package that your site uses. Enter RACF, ACF2, or TOPSEC.

This field corresponds to the EXTERNAL_SECURITY_PRODUCT parameter.

Allow Capture by USERID

The Global Recording by User ID flag. Global Recording supports the ability to record specified terminals and applications. To add the ability to capture 3270, LU0, or APPC activity based on user ID, enter Y in this field. Otherwise, enter N.

TCP/IP Global Recording parameters screen

Global Recording stores captured information in global capture buffers. The size and number of global capture buffers, along with a few other parameters, impact how often the buffers are flushed and processed, which impacts both Global Recording and system performance. Buffer settings that are too high or too low for the volume of traffic in your system may result in delayed recording request monitoring information, error messages, or even lost data due to slow processing or insufficient common storage.

Before completing the fields on this screen, determine the typical and peak volume, in kilobytes, of TCP/IP and MQ data that flows through your system.

The maximum number of TCP/IP connections expected to occur on the system at one time. Enter a value between 0 and 65,535. Upon startup, Global Recording creates information tracking tables in ECSA storage based on the specified maximum number of concurrent TCP/IP connections and the maximum number of simultaneous TCP/IP and MQ calls. If the actual counts are higher that these values, Global Recording has to allocate additional ECSA storage. While processing ECSA allocations, Global Recording may fall behind in processing captured traffic, which can produce error messages and compromise performance. Enter an accurate value to minimize CPU usage, eliminate unneeded data movement, and ensure optimum Global Recording and system performance.

This field corresponds to the MAXIMUM_TCP_CONNECTIONS parameter.

Number of recording buffers for both TCP/IP and WebSphere MQ

The number of buffers to use for recording TCP/IP and MQ traffic. Enter a number between 2 and 255. Set the buffer count high enough to accommodate peak volume. To determine the number of buffers required, multiply the peak-to-typical volume ratio by three or four. For example, if peak volume is 450K per second and typical volume is 150K per second (a ratio of 3:1), set the buffer count between 9 and 12.

This field corresponds to the TCP_MQ_ECSA_BUFFER_COUNT parameter.

Recording buffer size for both TCP/IP and WebSphere MQ, in KB

The size, in kilobytes, of each global capture buffer used to record TCP/IP and MQ traffic. Enter a number between 32K and 1024K. Global Recording typically flushes and processes the buffers as they fill. For optimum performance, Global Recording needs to flush and process one to two buffers per second. Use your typical data flow to determine the buffer size required for optimum performance. For example, if your typical data flow is 150K per second, set buffer size between 75K and 150K.

This field corresponds to the TCP_MQ_ECSA_BUFFER_SIZE parameter.

Maximum number of simultaneous TCP/IP and WebSphere MQ calls GR can track

The maximum number of TCP/IP and MQ calls expected to occur on the system at one time. Enter a value between 1 and 65,535. Upon startup, Global Recording creates information tracking tables in ECSA storage based on the specified maximum number of concurrent TCP/IP connections and the maximum number of simultaneous TCP/IP and MQ calls. If the actual counts are higher that these values, Global Recording has to allocate additional ECSA storage. While processing ECSA allocations, Global Recording may fall behind in processing captured traffic, which can produce error messages and compromise performance. Enter an accurate value to minimize CPU usage, eliminate unneeded data movement, and ensure optimum Global Recording and system performance.

This field corresponds to the MAXIMUM_CONCURRENT_TCP_MQ_CALLS parameter.

Maximum size TCP/IP Record to Record

The maximum TCP/IP record size to record, in kilobytes. The total buffer space available to capture a record is the buffer size multiplied by the number of buffers. If a record’s size exceeds the available buffer space, Global Recording loses data and generates error messages. To avoid this situation, set this value equal to or less than the total buffer space. Global Recording ignores any record that exceeds this value. To specify no limit, supply a value of 0.

This field corresponds to the MAXIMUM_TCP_RECORD_SIZE parameter.

Enable secure socket layer capture support?

The SSL support flag. Enter Y to enable Secured Socket Layer support. Otherwise, enter N.

This field corresponds to the TCP_SSL parameter.

Specify the Jobname of Open Edition (OMVS) address space

The job name of the Open Edition address space.

The field corresponds to the OMVS_JOBNAME parameter.

Specify up to eight TCP/IP Jobnames of address spaces eligible for capture

The names of the jobs that establish the address spaces that your users need to capture. If no jobnames are specified, TCP/IP capture is disabled.

This field corresponds to the TCPIP_JOBNAMES parameter.

Define virtual terminals screen

This screen presents three options:

1. Alphanumeric
2. Double-byte character set
3. Both.

The selection field defaults to option 1 Alphanumeric. Type the applicable option number and press Enter to continue.

The Guided Configuration builds custom samples based on the values you supply on the terminal definition screens. It also generates instructions in the manual task lists that explain what to do with the custom samples.

Complete all of the fields on this screen, then type G on the Command line and press Enter to create the terminal definition sample. If you plan to run Performance Test on multiple MVS systems, create definitions for each system. When all of the necessary samples are created, press End to continue to the next installation screen.

MVS SYSID for these terminal definitions

The ID of the MVS system to which the terminal definitions shall be assigned. Performance Test selects the appropriate terminals to use for playback based on the ID for the MVS system on which Performance Test is running. This field defaults to DFLT.

Terminal name prefix (1 to 7 Characters)

A prefix, up to seven alphanumeric characters, to apply to the terminal names. The terminal name prefix plus the length of the terminal name suffix must equal eight or fewer characters.

Terminal name suffix length

A length for the terminal name suffix. Supply a value between 1 and 7 that in combination with the terminal name prefix equals eight or fewer characters. For example, if the terminal prefix is MVSA, the suffix length can be 4, 3, 2, or 1.

Number of terminals to define

The number of terminals to define. Supply a value between 1 and 9999.

DLOGMODE (DEFAULT to use system default)

The name of the logon mode to apply to the terminal definitions. Either:

• Enter the name of an existing logon mode. This value must correspond to an entry in the default IBM logon mode table or to an entry in the table specified in the next field (MODETAB).
• Enter DEFAULT to omit the DLOGMODE parameter from the terminal definitions, which causes VTAM to select the appropriate value based on system settings.

This field holds up to 8 alphanumeric characters and defaults to DEFAULT.

MODETAB (DEFAULT to Use System Default)

The name of the logon mode table to apply to the terminal definitions. Either:

• Enter the name of the logon mode table that contains the entry specified in the DLOGMODE field.
• Enter DEFAULT to omit the MODETAB parameter from the terminal definitions, which causes VTAM to select the appropriate value based on system settings.

This field holds up to 8 alphanumeric characters and defaults to DEFAULT.

Define LU Type 2 DBCS virtual terminals screen

Complete all of the fields on this screen, then type G on the Command line and press Enter to create the terminal definition sample. If you plan to run Performance Test on multiple MVS systems, create definitions for each system. When all of the necessary samples are created, press End to continue to the next installation screen.

MVS SYSID for these terminal definitions

The ID of the MVS system to which the terminal definitions shall be assigned. Performance Test selects the appropriate terminals to use for playback based on the ID for the MVS system on which Performance Test is running. This field defaults to DFLT.

Terminal name prefix (1 to 7 Characters)

A prefix, up to seven alphanumeric characters, to apply to the terminal names. The terminal name prefix plus the length of the terminal name suffix must equal eight or fewer characters.

Terminal name suffix length

A length for the terminal name suffix. Supply a value between 1 and 7 that in combination with the terminal name prefix equals eight or fewer characters. For example, if the terminal prefix is MVSA, the suffix length can be 4, 3, 2, or 1.

Number of terminals to define

The number of terminals to define. Supply a value between 1 and 9999.

DLOGMODE (DEFAULT to use system default)

The name of the logon mode to apply to the terminal definitions. Either:

• Enter the name of an existing logon mode. This value must correspond to an entry in the default IBM logon mode table or to an entry in the table specified in the next field (MODETAB).
• Enter DEFAULT to omit the DLOGMODE parameter from the terminal definitions, which causes VTAM to select the appropriate value based on system settings.

This field holds up to 8 alphanumeric characters and defaults to DEFAULT.

MODETAB (DEFAULT to use system default)

The name of the logon mode table to apply to the terminal definitions. Either:

• Enter the name of the logon mode table that contains the entry specified in the DLOGMODE field.
• Enter DEFAULT to omit the MODETAB parameter from the terminal definitions, which causes VTAM to select the appropriate value based on system settings.

This field holds up to 8 alphanumeric characters and defaults to DEFAULT.

Define LU Type 0 Virtual Terminals Screen

Complete all of the fields on this screen, then type G on the Command line and press Enter to create the terminal definition sample. When all of the necessary samples are created, press End to continue to the next installation screen.

Terminal name prefix (1 to 7 Characters)

A prefix, up to seven alphanumeric characters, to apply to the terminal names. The terminal name prefix plus the length of the terminal name suffix must equal eight or fewer characters.

Terminal name suffix length

A length for the terminal name suffix. Supply a value between 1 and 7 that in combination with the terminal name prefix equals eight or fewer characters. For example, if the terminal prefix is MVSA, the suffix length can be 4, 3, 2, or 1.

Number of terminals to define

The number of terminals to define. Supply a value between 1 and 9999.

DLOGMODE (DEFAULT to use system default)

The name of the logon mode to apply to the terminal definitions. Either:

• Enter the name of an existing logon mode. This value must correspond to an entry in the default IBM logon mode table or to an entry in the table specified in the next field (MODETAB).
• Enter DEFAULT to omit the DLOGMODE parameter from the terminal definitions, which causes VTAM to select the appropriate value based on system settings.

This field holds up to 8 alphanumeric characters and defaults to DEFAULT.

MODETAB (DEFAULT to use system default)

The name of the logon mode table to apply to the terminal definitions. Either:

• Enter the name of the logon mode table that contains the entry specified in the DLOGMODE field.
• Enter DEFAULT to omit the MODETAB parameter from the terminal definitions, which causes VTAM to select the appropriate value based on system settings.

This field holds up to 8 alphanumeric characters and defaults to DEFAULT.

Define APPC APPLIDs screen

To play back an APPC conversation, Performance Test for Mainframe Servers requires a VTAM LU, defined as an application (APPLID). It requires one APPLID for each playback job. The Guided Configuration creates a member containing customized APPLIDs based on the values you supply on this screen. It also generates instructions in the manual task lists that explain what to do with the generated member.

Complete all of the fields on this screen, type G on the Command line, and press Enter to create the APPLID definitions sample.

APPLID name prefix (1 to 7 characters)

A prefix, up to seven alphanumeric characters, to apply to the application IDs. The APPLID name prefix plus the length of the APPLID name suffix must equal eight or fewer characters.

APPLID name suffix length

A length for the application ID name suffix. Supply a value between 1 and 7 that in combination with the APPLID name prefix equals eight or fewer characters. For example, if the terminal prefix is APPC, the suffix length can be 4, 3, 2, or 1.

DLOGMODE

The name of the logon mode to apply to the APPLID. Enter the name of an existing logon mode. This value must correspond to an entry in the default IBM logon mode table or to an entry in the table specified in the next field (MODETAB).

This field holds up to 8 alphanumeric characters and defaults to #INTER.

MODETAB

The name of the logon mode table to apply to the terminal definitions. Either:

• Enter the name of the logon mode table that contains the entry specified in the DLOGMODE field.
• Enter DEFAULT to omit the MODETAB parameter from the APPLIDs, which causes VTAM to select the appropriate value based on system settings.

This field holds up to 8 alphanumeric characters and defaults to DEFAULT.

Number of APPLs with parallel session

The number of definitions to create with parallel session support parameters. Supply a numeric value between 0 and 9999. Set this value high enough to accommodate the expected maximum number of simultaneous APPC playback jobs.

The number of definitions to create without parallel session support parameters. Supply a numeric value between 0 and 9999. Set this value high enough to accommodate the expected maximum number of simultaneous APPC playback jobs.

Performance Testreports are generated with batch jobs. Set up one or more system-level reporting asset libraries to store members containing sample JCL and SYSIN parameters. Populate the libraries with reporting assets that are tailored for your users. For example, create sample jobs for different types of reports or for different groups.

To create a library, complete all of the fields on this screen, type G on the Command line, and press Enter. When you have finished creating libraries, press End to continue to the next installation screen.

The name of the reporting asset library. Either accept the default or enter a data set name. This field holds up to 44 characters. It defaults to a data set name that begins with the high-level qualifier that you specified earlier, followed by HS.REPORT.

DASD Esoteric Unit

The device on which to store the library. This field defaults to SYSDA.

Enable ISPF edit macros screen

Complete the field and press Enter. The Guided Configuration copies the appropriate procedures in the specified procedure library and continues to the next installation screen.

User procedure library

The procedure library to contain the LOCPOS, BRULE, and BRULES procedures. These procedures enable the length and offset determination macros, which aid users with writing dynamic data-replacement logic. Specify a library in the user’s TSO SYSPROC concatenation.

Set up reporting asset library for TCP/IP screen

TCP/IP testing reports are generated with batch jobs. Set up one or more system-level reporting asset libraries to store members containing sample JCL and SYSIN parameters.

Complete all of the fields on this screen, type G on the Command line, and press Enter. The Guided Configuration creates the specified library and populates it with several reporting asset samples. When you have finished creating libraries, press End to continue to the next installation screen.

The name of the reporting asset library. Either accept the default or enter a data set name. This field holds up to 44 characters. It defaults to a data set name that begins with the high-level qualifier that you specified earlier, followed by HS.REPORT.

DASD Esoteric Unit

The device on which to store the library. This field defaults to SYSDA.

Web-Based Reporting

Fill in the Web Directory field, type G on the Command line, and press Enter. The Guided Configuration creates the web directory and its subdirectories. It populates each subdirectory with assets required by the web-based reporting feature. Press End to continue with the next installation screen.

Web Directory

The OMVS directory to contain JavaScript, images, REXX, and other web elements used by the web-based reporting feature. This field defaults to the value that you supplied when you built the SMP/E environment. This value must begin with a forward slash (/), it can be up to 39 characters, and it cannot contain spaces. Mixed case entries are preserved.

External Security Interface Settings Screen

Complete the fields on this screen and press Enter to continue to the next installation screen.

Security Class name

The security, or resource, class name. The class name can be one to eight alphanumeric characters. For a list of resource classes, refer to IBM’s RACF Macros and Interfaces. The default value, NOSECURITY, disables function-access security.

Security Entity Name

The security entity name. The entity name can be one to eight alphanumeric characters. This is the high-level qualifier for the resource names that Performance Test checks. For example, if a user attempts to access the Domain Traveler function, and you have accepted the default value of HIPER, Performance Test checks HIPER.FN.TESTING.

This field corresponds to the SECURITY_CLASS_ENTITY parameter.

Security Volume ID

The volume ID that Performance Test specifies on the call to the security package when the class name is set to DATASET. This field holds up to six alphanumeric characters. The default value is HIPERX.

Enable custom signon security screen

At playback time, Performance Test for Mainframe Servers uses the criteria specified on this screen to determine if the 3270 script contains a signon screen and to determine where on the screen to look for the user ID.

To define criteria, modify the HSCM PARMLIB member. Set parameter ENABLE_CUSTOM_SIGNON_SECURITY to YES to enable the custom signon security checking. Code one SIGNON_ENTRY through END entry for each signon screen. Each entry must specify:

ROW

The row containing the user ID.

COLUMN

The column in which the user ID begins.

LENGTH

The length of the user ID field.

STRING

A string, up to 255 characters, unique to the signon screen. Performance Test uses this information to determine if the screen is a signon screen.

Install Performance Test for WebSphere MQ Screens

This section defines the fields on the Performance Test for WebSphere MQ installation screens.

Establish access to the Product Suite screen

The Guided Configuration uses the LIBDEF utility to set up the ISPF environment. After you complete the following fields and press Enter, the Guided Configuration creates the CLIST member and copies it into specified CLIST library.

Performance Test CLIST name

The name of a member to contain the Performance Test CLIST. The Guided Configuration creates this member. The default value is LIBDEF.

CLIST Library

The CLIST library in your user’s TSO SYSPROC concatenation into which the Performance Test CLIST can be placed. The default value is the install library from which Guided Configuration was executed.

Create Global Recording request file screen

Performance Testrequires a data set to track information from the Global Recording features. Global Recording uses this data set to store recording request records and include/exclude lists.

Complete all of the fields on this screen, type G on the Command line, and press Enter to create the data set. If you plan to run Performance Test on multiple MVS systems that share DASD, create a data set for each system. When all of the necessary data sets are created, press End to continue to the next installation screen.

GRREQ DSN

A name for the request data set. Enter a valid data set name up to 38 characters. This field defaults to a DSN that starts with your TSO user ID and the Performance Test build number, and ends with GRREQ.

The number of cylinders to allocate for the file. This field’s default value is 5.

Secondary allocation

The number of additional cylinders to allocate if the primary allocation is exceeded. The default value is 1.

Volumes

The serial number of the volume on which to store the request data set. This field accepts up to six alphanumeric characters.

Install Global Recording started task

Global Recording is accomplished through the use of an MVS started task. After you complete the following fields and press Enter, the Guided Configuration prepares the started task JCL and copies it into the specified procedure library.

The system procedure library in which to place the started task JCL. This field defaults to the install library from which the Guided Configuration is running.

Task name

A name for the member that will contain the Global Recording started task JCL. This field defaults to GRTASK.

MQ Global Recording parameters screen

Global Recording stores captured information in global capture buffers. The size and number of global capture buffers, along with a few other parameters, impact how often the buffers are flushed and processed, which impacts both Global Recording and system performance. Buffer settings that are too high or too low for the volume of traffic in your system may result in delayed recording request monitoring information, error messages, or even lost data due to slow processing or insufficient common storage.

Before completing the fields on this screen, determine the typical and peak volume, in kilobytes, of TCP/IP and MQ data that flows through your system.

The maximum number of MQ queue manager connections plus the maximum number of objects (queues) expected to be open on the system at one time. Enter a value between 0 and 65,535. Upon startup, Global Recording creates information tracking tables in ECSA storage based on this value and the maximum number of simultaneous TCP/IP and MQ calls. If the actual counts are higher that these values, Global Recording has to allocate additional ECSA storage. While processing ECSA allocations, Global Recording may fall behind in processing captured traffic, which can produce error messages and compromise performance. Enter an accurate value to minimize CPU usage, eliminate unneeded data movement, and ensure optimum Global Recording and system performance.

This field corresponds to the MAXIMUM_MQ_CONNECTIONS parameter.

Subsystem ID of any DEFINED WebSphere MQ subsystem

The four-character ID of any MQ Subsystem that is defined in the MVS Subsystem Name table.

This field corresponds to the MQ_QUEUE_MANAGER_NAME parameter.

Number of recording buffers for both TCP/IP and WebSphere MQ

The number of buffers to use for recording TCP/IP and MQ traffic. Enter a number between 2 and 255. Set the buffer count high enough to accommodate peak volume. To determine the number of buffers required, multiple the peak-to-typical volume ratio by three or four. For example, if peak volume is 450K per second and typical volume is 150K per second (a ratio of 3:1), set the buffer count between 9 and 12.

This field corresponds to the TCP_MQ_ECSA_BUFFER_COUNT parameter.

Recording buffer size for both TCP/IP and WebSphere MQ, in KB

The size, in kilobytes, of each global capture buffer used to record TCP/IP and MQ traffic. Enter a number between 32K and 1024K. Global Recording typically flushes and processes the buffers as they fill. For optimum performance, Global Recording needs to flush and process one to two buffers per second. Use your typical data flow to determine the buffer size required for optimum performance. For example, if your typical data flow is 150K per second, set buffer size between 75K and 150K.

This field corresponds to the TCP_MQ_ECSA_BUFFER_SIZE parameter.

Maximum number of simultaneous TCP/IP and MQ calls GR can track

The maximum number of TCP/IP and MQ calls expected to occur on the system at one time. Enter a value between 1 and 65,535. Upon startup, Global Recording creates information tracking tables in ECSA storage based on the specified maximum number of concurrent TCP/IP connections and the maximum number of simultaneous TCP/IP and MQ calls. If the actual counts are higher that these values, Global Recording has to allocate additional ECSA storage. While processing ECSA allocations, Global Recording may fall behind in processing captured traffic, which can produce error messages and compromise performance. Enter an accurate value to minimize CPU usage, eliminate unneeded data movement, and ensure optimum Global Recording and system performance.

This field corresponds to the MAXIMUM_CONCURRENT_TCP_MQ_CALLS parameter.

Filter out syncpoint events not relevant to playback (Y/N)?

The syncpoint filtration flag. Enter Y to have Global Recording capture only relevant “syncpoint” events—that is, the MQ COMMITs and BACKOUTs associated with the recorded GET, PUT, or SET events. Eliminating irrelevant “syncpoint” events from capture can result in smaller repositories and lower processing requirements for script creation. Enter N to have Global Recording capture all “syncpoints”.

This field corresponds to the MQ_SYNCPOINT parameter.

Maximum size TCP and WebSphere MQ record to record (0 = no limit)

The maximum MQ or TCP/IP record size to record, in kilobytes. The total buffer space available to capture a record is the buffer size multiplied by the number of buffers. If a record’s size exceeds the available buffer space, Global Recording loses data and generates error messages. To avoid this situation, set this value equal to or less than the total buffer space. Global Recording ignores any record that exceeds this value. To specify no limit, enter a value of 0.

This field corresponds to the MAXIMUM_TCP_RECORD_SIZE parameter.

Temporary data set allocation for MQ reporting screen

Specify allocation parameters for the temporary CSV data set that Performance Test for WebSphere MQ creates while generating the HTML Event Summary.

DASD unit

The DASD unit name on which to store the temporary data set. This is a required field, and it defaults to SYSDA.

This field corresponds to the TEMPORARY_UNIT parameter.

Volume (leave blank to exclude)

The volume on which to store the temporary data set. Leave this field empty to exclude the volume parameter from the allocation statement.

This field corresponds to the TEMPORARY_VOLUME parameter.

Space allocation (CYLS, TRKS, or BLKS)

The space units to allocate for the data set. Enter CYLS for cylinders, TRKS for tracks, or BLKS for blocks. This is a required field, and it defaults to CYLS.

This field corresponds to the TEMPORARY_SPACE_UNITS parameter.

Primary allocation

The initial number of space units to allocate for the temporary data set. This is a required field, and it defaults to 7.

This field corresponds to the TEMPORARY_PRIMARY_ALLOCATION parameter.

Secondary allocation

The number of additional space units to allocate if the temporary data set requires more space. This is a required field, and it defaults to 3.

This field corresponds to the TEMPORARY_SECONDARY_ALLOCATION parameter.

SMS management class (leave blank to exclude)

The SMS management class to apply to the data set allocation. Leave this field empty to exclude the management class parameter from the allocation statement.

This field corresponds to the TEMPORARY_MANAGEMENT_CLASS parameter.

SMS storage class (leave blank to exclude)

The SMS storage class to apply to the data set allocation. Leave this field empty to exclude the storage class parameter from the allocation statement.

This field corresponds to the TEMPORARY_STORAGE_CLASS parameter.

SMS data class (leave blank to exclude)

The SMS data class to apply to the data set allocation. Leave this field empty to exclude the data class parameter from the allocation statement.

This field corresponds to the TEMPORARY_DATA_CLASS parameter.

Enable ISPF Edit Macros Screen

Complete the field and press Enter. The Guided Configuration copies the appropriate procedures in the specified procedure library and continues to the next installation screen.

User Procedure Library

The procedure library to contain the LOCPOS, BRULE, and BRULES procedures. These procedures enable the length and offset determination macros, which aid users with writing dynamic data-replacement logic. Specify a library in the user’s TSO SYSPROC concatenation.

Set Up WebSphere MQ Playback and Reporting Asset Libraries Screen

Performance Testfor WebSphere MQ playback and reporting features are batch driven. Set up system-level playback and reporting asset libraries to contain sample JCL and SYSIN parameters.

Additionally, the Performance Test for WebSphere MQ User space provides several comprehensive testing examples based on a real test system. To help users conceptualize data filtration procedures, the repository containing the recorded test system data is supplied.

Complete all of the fields on this screen, type G on the Command line, and press Enter. The Guided Configuration creates the specified libraries and populates them with several samples. When you have finished creating libraries, press End to continue to the next installation screen.

The name of the library to contain the playback control samples. Either accept the default or enter a data set name. This field holds up to 44 characters. It defaults to a data set name that begins with the high-level qualifier that you specified earlier, followed by MQ.CONTROL.

Reporting control library

The name of the library to contain the reporting control samples. Either accept the default or enter a data set name. This field holds up to 44 characters. It defaults to a data set name that begins with the high-level qualifier that you specified earlier, followed by MQ.REPORT.

Sample Repository data set

The name of the data set to contain the sample capture repository that supports the examples provided in the Performance Test for WebSphere MQ User space. Either accept the default or enter a data set name. This field holds up to 44 characters. It defaults to a data set name that begins with the high-level qualifier that you specified earlier, followed by MQ.REPOS.

DASD esoteric unit

The device on which to store the libraries. This field defaults to SYSDA.

User procedure library

The user procedure library to contain the playback and reporting procedures (PROC). This field defaults to name of the install library from which the Guided Configuration was executed.

Web-Based reporting screen

Fill in the Web Directory field, type G on the Command line, and press Enter. The Guided Configuration creates the web directory and its subdirectories. It populates each subdirectory with assets required by the web-based reporting feature. Press End to continue to the next installation screen.

Web Directory

The OMVS directory to contain JavaScript, images, REXX, and other web elements used by the web-based reporting feature. This field defaults to the value that you supplied when you built the SMP/E environment. This value must begin with a forward slash (/), it can be up to 39 characters, and it cannot contain spaces. Mixed case entries are preserved.

External security interface settings screen

Complete the fields on this screen and press Enter to continue to the next installation screen.

Security class name

The security, or resource, class name. The class name can be one to eight alphanumeric characters. For a list of resource classes, refer to IBM’s RACF Macros and Interfaces. The default value, NOSECURITY, disables function-access security.

Security entity name

The security entity name. The entity name can be one to eight alphanumeric characters. This is the high-level qualifier for the resource names that Performance Test checks. For example, if a user attempts to access the Domain Traveler function, and you have accepted the default value of HIPER, Performance Test checks HIPER.FN.TESTING.

This field corresponds to the SECURITY_CLASS_ENTITY parameter.

Security volume ID

The volume ID that Performance Test specifies on the call to the security package when the class name is set to DATASET. This field holds up to six alphanumeric characters. The default value is HIPERX.

Configure SIEM Data Delivery

Performance Testfor WebSphere MQ can be configured to deliver Security Incident and Event Management (SIEM) data to analytics and reporting tools, such as Splunk^®.

1. Use the SIEM Tool Data Generation Parameters screen to specify where your site’s SIEM data should be sent as follows:
   1. If your SIEM product has a listening port that can accept Performance Test MQ data, type 1 in the Select destination for SIEM data field.
   2. Under TCP address of SIEM listener, enter the IP address and port number on which your SIEM product is installed and listening. The mainframe must be able to connect to the machine where your SIEM product is installed.
2. Press Enter to store the SIEM tool data generation parameters and continue, or Cancel to exit.