Performance Test for Mainframe Servers Profile Defaults (MF User)
APPC profile defaults
The APPC Record and Script Create Defaults settings allow you to specify only the APPC conversations you want to record by supplying field values that identify those conversations. Only the APPC conversations that match all your field values will be recorded. The fields are logically linked together using 'AND'.
Select option 2 APPC from the Edit Profile screen. The APPC Record and Script Create Defaults screen is displayed.
Performance Test for Mainframe Servers - Edit Profile screen--------------------------------- Edit Profile --------------------------------
Command ===>
More: +
Primary commands: menu-number, ALL, CANCEL
Line commands: S or / to select options.
Active Profile:
Dataset ===> 'PMIJSS0.JMS.ATV.PROFILE'
Member ===> PROFILE
Description ===> COPY FOR THE JAKEATV
1 Domain Traveler Recording and Playback defaults
2 APPC Global Record and Script Create settings
3 3270/LU0 Global Record and Script Create settings
4 WebSphere MQ Global Record and Script Create settings
5 TCP/IP Global Record and Script Create settings
6 Playback MQ MQ Playback parameter defaults
7 Playback TCP TCP Playback parameter defaults
8 ATV Manager Test Vehicle defaults
Should changes made elsewhere to Profile values be saved?
Profile Autosave ===> Y (Y = YES, N = NO OR A = ASK)APPC Record and Script Create Defaults - Record Settings
-------------------- APPC Record and Script Create Defaults ------ Top of data
Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE'
OPTION ===>
More: +
--------------------------------Record settings--------------------------------
Capture Criteria:
Side A LU ===> (Logical unit name or *)
Side A Netid ===>
Side B LU ===> (Logical unit name or *)
Side B Netid ===>
Logmode ===> (VTAM logmode name or *)
User ID ===> PMIJSS* (userid or *)
TP Name ===>
Start and End times:
Date and Time HH : MM : SS MM / DD / YY
Start Time ===> 00 : 00 : 00 Start Date 00 / 00 / 00
End Time ===> 23 : 59 : 00 End Date 02 / 15 / 23
Repository Dataset:
Dataset Name ===> 'PMIJSS0.APPCEX.REPOS*'
First Number ===> 1 (if wildcard in dataset)
Last Number ===> 5 (if wildcard in dataset)
Recording options: (Enter "/" to select)
/ Suspend Script Creation
/ FORCE Request at 'End Time'
Normal Event Notification
Error Event Notification- Fill in or change the Record settings fields. The fields in this group are all optional.
- Side A LU and Side B LU (optional) contain the VTAM LU name for one of the partners that make up the APPC conversation you want to capture. Wildcards are allowed. If you leave both of these fields blank, you will capture all APPC activity on this MVS system. If you enter a value in either the Side A LU or Side B LU field and leave the other blank, conversations involving the particular LU name will be captured.
- Side A Netid and Side B Netid (optional) contain the VTAM Network ID for the Side A and Side B LU partner. Only supply values for these fields if you want to restrict data capture to APPC conversations between logical units on specific VTAM networks. One of those networks must be the one on which the VTAM on this MVS system is running.
- Logmode (optional) contains the VTAM logon mode name and specifies some of the characteristics of the session.
- User ID (optional) contains the user ID passed between APPC partners when a conversation begins. The user ID is used by one partner to validate the other partner. Since not all APPC conversations pass a user ID, if you enter a user ID value, only those APPC conversations that pass the value will be recorded.
- TP Name (optional) contains the transaction program name. It identifies the program located at the partner’s logical unit that is to be run. TP names can be from 1 to 64 characters and can contain non-printable values. If the TP name contains only printable values and no blanks, you can supply the TP name with no quotation marks. If the TP name contains blanks, enclose the TP name in single quotation marks. Letters will not be converted to uppercase since TP names may contain lowercase letters. If the TP name contains non- printable values, type the TP name in hexadecimal, enclose it in single quotation marks and either prefix the first quote or suffix the last quote with the letter X. For example, the CNOS transaction is entered as X'06F1' or '06F1'X.
- Start and End Date and Time are optional fields that specify the date and time of day that you want the capture request to be started or stopped. If you enter a Start Time, you must enter a Start Date. If you enter an End Time, you must enter an End Date.
- Specify your Repository Dataset options.
- Dataset Name is required and specifies where captured data will be stored on DASD. You can enter a fully qualified data set name up to 44 characters to allocate a fixed repository. You can also enter a data set name with a wildcard of “*” or “?” to allocate a repository set. This set is defined by a range of numbers specified in the First Number and Last Number fields. Entering an “*” in the data set name expands the qualifier to eight characters and fills with zeros (for example, xyz* would result in XYZ00001). Entering one or more “?”s in the data set name replaces those character positions with numbers (for example, XYZ??ABC would result in XYZ01ABC).
- First Number and Last Number define the range of data sets for your repository set. You can enter any range from 0 to 9999999. When one data set fills up, it is closed and data continues to be written to the next data set in sequence. These fields are required if you enter a wildcard in the Repository Dataset name field.
Specify your Recording options
Recording options define the way your capture request will generate scripts, process the repository, stop your requests, and send normal and/or error messages.
Enter a slash (/) to select the following options:- Suspend Script Creation controls automatic script creation. Enter a slash (/) to defer script creation when your capture request stops. It also defers the entry of script creation criteria to a later time. If you leave this field blank, you will be guided through the script creation criteria screens prior to your capture request being activated, and your scripts will be created automatically when your capture request is stopped.
- FORCE Request at 'End Time' controls whether your capture request is forced rather then stopped when it reaches the End Time specified in your request. A forced request is stopped immediately regardless of whether the sessions you are capturing have ended. A stopped request is deactivated so no new sessions will be captured. In-flight sessions continue to be captured until a session logoff occurs. If you leave this field blank, your capture request will be stopped rather then forced when it reaches the End Time in your request. This field can only be selected if you entered an End Time in your request.
- Normal Event Notification and Error Event Notification control whether normal and error event messages are generated and sent to your TSO session. Enter a slash (/) to receive these messages at your terminal, or leave blank for no messages to be sent.
- Error Event Notification controls whether error event messages are generated and sent to your TSO session. If you enter a slash (/) in this field, you will receive these messages at your terminal. If you leave it blank, no messages will be sent.
APPC Record and Script Create Defaults - Script Create Settings
-------------------- APPC Record and Script Create Defaults ------ Top of data
Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE'
OPTION ===>
More: +
-----------------------------Script Create Settings----------------------------
Script Dataset
Dataset Name ===> 'PMIJSS0.APPCEX.SCRIPTS'
Prefix ===> SCR (1 - 6 character prefix)
Suffix ===> 0000000 (2 - 7 numeric suffix)
Replace? ===> N (Y = Yes, N = No)
Script Content:
Where Should Details be Stored: (Enter number to select)
1 1. Merged into the script
2. Separate from the script, input and output together
3. Separate from the script, input and output split
What Should be Recorded: (Enter "/" to select)
/ Conversation Log
/ Script
/ Script
/ Details
Script Create Options: (Enter "/" to select)
Suppress time stamps in script
Write script tags in short CPIC format
Write all PIU traffic as script comments
Include SNA service transactions (logmodes: SNASVCMG,
CPSVCMG, CPSVRMGR)
Script Create Execution Options:
Select processing option: (Enter number to select)
1 1. Submit batch job
2. TSO
Other Datasets:
Conversation Log
Dataset Name ===> 'PMIJSS0.APPCEX.LOG'
Prefix ===> LOG (1 - 6 character prefix)
Suffix ===> 0000000 (2 - 7 numeric suffix)
Replace? ===> (Y = Yes, N = No)
Combined Detail ===>
Conversation Log
Dataset Name ===> 'PMIJSS0.APPCEX.LOG'
Prefix ===> LOG (1 - 6 character prefix)
Suffix ===> 0000000 (2 - 7 numeric suffix)
Replace? ===> (Y = Yes, N = No)
Combined Detail ===>
Prefix ===> (1 - 6 character prefix)
Suffix ===> 0000000 (2 - 7 numeric suffix)
DDname ===>- Specify the Script Create Settings
- Script Dataset, Dataset Name, Prefix, and Suffix specify the fully-qualified data set and member names where you want to store your scripts.
- Replace? specifies whether the script data set will replace a data set of the same name. Enter Y or N.
Specify your Script Content options.
Script Content fields specify where to store the detail data for your scripts, what to record, and how to process your script data sets.- Where Should Details be Stored is a required field that specifies where on DASD to store the APPC message details in relationship to your scripts. You must choose one of the following options. Enter a number to make your selection.
- Merged into the script places the detail data into the same PDS member as the script. APPC verbs contained in the script will be merged with the data sent by the verbs. This option allows you to view all data for a conversation in a single PDS member.
- Separate from the script, inbound and outbound together places the detail data into a PDS member that is separate from the script PDS member. This option keeps the script member uncluttered with (possibly) non-printable data. In addition, a file-formatting tool can be used to display the detail data since it is now separate from the APPC verbs.
- Separate from the script, inbound and outbound split places the detail data into two PDS members, both of which are separate from the script member. One member contains outbound data, and the other member contains inbound data. Outbound refers to all data sent by the logical unit that started the APPC conversation (issued the ALLOCATE verb). Inbound refers to all data sent by the other logical unit.
- Specify What Should be Recorded options.
These options define what you will create from your captured data when requesting script creation processing. Enter a slash (/) to make your selection. You can select one or more of the following options:- Conversation Log creates a single conversation log for each of your capture requests. The log contains a list of every APPC conversation (ALLOCATE statement) that has been captured by your request. After each ALLOCATE statement is a SCRIPT statement naming the PDS member containing the entire APPC conversation. The conversation log is written when you issue the Stop or Force line command from the Global Record Monitor Requests screen. The conversation log, after some modifications, is typically used as the SYSIN data set for your playbacks.
- Script creates a new script for every APPC conversation that was captured by your request. Each script is placed in a different member of a PDS. The name of each member is also entered in the conversation log on the SCRIPT statement. In this way, the conversation log points to every script that was created. A script contains all of the APPC verbs (ALLOCATE, SEND, RECEIVE, etc.) issued by the two partners in the APPC conversation.
- Details writes the details for every APPC conversation that was captured by your request. 'Details' is the term used for the data sent by the APPC partners to each other. It might be human-readable data, or it might consist of only binary data.
- Fill in or change the Script Create Options. Enter a slash (/) to make your selection.
- Suppress time stamps in script omits time stamps making the script easier to browse. If you are reviewing the scripts for debugging purposes, select this option to make the scripts easier to read. Performance Test uses time stamps to synchronize playback. If you intend to play back scripts at the same pace as they were recorded, do not select this option.
- Write script tags in short CPIC format writes APPC verbs in Common Programming Interface for Communications (CPIC) format, rather than Performance Test proprietary format. For example, a send verb appears in the script as CMSEND rather than SEND_DATA. This option is for readability and has no impact on playback.
- Write all PIU traffic as script comments writes VTAM Path Information Units (PIUs) into the script (the 26-byte Transmission Headers (TH), the 3-byte Request Headers (RH), and the variable length Request Units (RU) that are sent between VTAM logical units). In the scripts, this information appears in CONTENT tags under a PIU tag. Although the information does not appear with the traditional comment indicator (*) in column one, playback ignores the PIU block of tags. This option supports debugging VTAM applications.
- Include SNA service transactions writes special APPC conversations used by subsystems such as VTAM and CICS into the scripts. For example, the Change Number of Session (CNOS) and Exchange Log Name (XLN) transactions appear in the script if you select this option. These conversations use the following logmodes: SNASVCMG, CPSVCMG, or CPSVRMGR. This option supports application debugging and does not impact playback.
- Script Create Execution Options specifies whether you want background (batch) or foreground processing to be your default. Select 1 (background) or 2 (foreground). Sample JCL is provided for a batch job, which you can change if desired.
- Several Other Datasets will be created. You can change the data set name, prefix, suffix, DDname, etc. if desired.
- The Conversation Log data set specifies where you want the conversation log to reside on DASD. If you allocate this data set as a PDS or PDSE, you must enter a member name prefix value and a numeric suffix value unless you want the default value of zero.
- The Combined Detail data set specifies where you want the combined inbound and outbound message data to reside on DASD. This data set must be allocated as a PDS or PDSE, and you must enter a member name prefix value, a numeric suffix value (unless you want the default value of zero), and a unique 8-character DDname value. The DDname you supply is written into the script member along with the APPC verbs. This enables Performance Test to find your detail data when you play back the script. You must place the same DDname in the JCL used to play back your scripts.
- The Outbound Detail data set specifies where you want the outbound detail message data to reside on DASD. This data set must be allocated as a PDS or PDSE, and you must enter a member name prefix value in the PREFIX column, a numeric suffix value in the SUFFIX column (unless you want the default value of zero), and a unique 8-character DDname value. The DDname you supply is written into the script member along with the APPC verbs. This enables Performance Test to find your detail data when you play back the script. You must place the same DDname in the JCL used to play back your scripts.
- The Inbound Detail data set specifies where you want the inbound detail message to reside on DASD. This data set must be allocated as a PDS or PDSE, and you must enter a member name prefix value in the PREFIX column, a numeric suffix value in the SUFFIX column (unless you want the default value of zero), and a unique 8-character DDname value. The DDname you supply is written into the script member along with the APPC verbs. This enables Performance Test to find your detail data when you play back the script. You must place the same DDname in the JCL used to play back your scripts.
TCP/IP profile defaults
This section specifies the TCP/IP Global Recording and Script Create defaults.
Select option 5 TCP/IP from the Edit Profile screen. The TCP/IP Global Record/Script Create Defaults screen is displayed.
Edit Profile screen--------------------------------- Edit Profile --------------------------------
Command ===>
More: +
Primary commands: menu-number, ALL, CANCEL
Line commands: S or / to select options.
Active Profile:
Dataset ===> 'PMIJSS0.JMS.ATV.PROFILE'
Member ===> PROFILE
Description ===> COPY FOR THE JAKEATV
1 Domain Traveler Recording and Playback defaults
2 APPC Global Record and Script Create settings
3 3270/LU0 Global Record and Script Create settings
4 WebSphere MQ Global Record and Script Create settings
5 TCP/IP Global Record and Script Create settings
6 Playback MQ MQ Playback parameter defaults
7 Playback TCP TCP Playback parameter defaults
8 ATV Manager Test Vehicle defaults
Should changes made elsewhere to Profile values be saved?
Profile Autosave ===> Y (Y = YES, N = NO OR A = ASK)TCP/IP Global Record/Script Create Defaults - Record Settings
--------------------------------Record Settings--------------------------------
Create Recording Filters (/ for Filter Create panel)
Repository Dataset:
Dataset Name ===> 'PMIJSS0.SMOKET.D23.REPOS*'
First Number ===> 1 (if wildcard in dataset)
Last Number ===> 5 (if wildcard in dataset)
Reuse Repository Options: (Enter "/" to select)
/ Delete existing data
Append to existing data
/ Overwrite existing data when all segments are full
Amount of Data to Record:
Data from client ===> ALL (ALL/number)
Data from server ===> ALL (ALL/number)- In the Create Recording Filters field, enter a slash (/) to display the TCP/IP Data Collect screen where you can create recording filters. See TCP/IP Scripts and Subset Repositories or the online help for information about creating filters.
- Specify your Repository Dataset options.
- Dataset Name is required and specifies where captured data will be stored on DASD. You can enter a fully qualified data set name up to 44 characters to allocate a fixed repository. You can also enter a data set name with a wildcard of “*” or “?” to allocate a repository set. This set is defined by a range of numbers entered in the First Number and Last Number fields. Entering an “*” in the data set name expands the qualifier to eight characters and fills with zeros (for example, xyz* would result in XYZ00001). Entering one or more “?”s in the data set name replaces those character positions with numbers (for example, XYZ??ABC would result in XYZ01ABC).
- First Number and Last Number define the range of data sets for your repository set. You can enter any range from 0 to 9999999. When one data set is full, it is closed and data continues to be written to the next data set in sequence. These fields are required if you entered a wildcard in the Repository Dataset Name field.
- Reuse Repository Options specifies the way your capture request will process the repository. Enter a slash (/) to select.
- Delete existing data allows capture to start writing data to the beginning of the repository or the first segment of a repository set. Any data that exists will be overwritten. This selection is mutually exclusive with Append to existing data.
- Append to existing data allows capture to add data to the repository (or the last segment of a repository set that was capturing data. Any data that exists will be preserved. This selection is mutually exclusive with Delete existing data.
- Overwrite existing data when all segments are full continues writing captured data to the first segment of a repository set when the last segment is full. This option is valid only when using a repository set.
Amount of Data to Record can record any TCP/IP data that passes through this MVS system and matches your filtering criteria. To record all of that data, enter ALL in Data from client and Data from server. Otherwise, any non-zero numeric value will limit the amount of data recorded from a single message to a number of bytes.
TCP/IP Global Record/Script Create Defaults - Script Create Settings
----------------- TCP/IP Global Record/Script Create Defaults -----------------
Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE'
OPTION ===>
More: +
-----------------------------Script Create Settings----------------------------
Create Script Filters (/ for Filter Create panel)
Repository Dataset:
Dataset Name ===>
Dataset Name ===>
First Number ===> (if wildcard in dataset)
Last Number ===> (if wildcard in dataset)
Amount of Data to Use:
Data from Client ===> ALL (ALL/number)
Data from Server ===> ALL (ALL/number)
Script Content:
Where Should Details be Stored: (Enter number to select)
1 1. Merged into the script
2. Separate from the script, input and output together
3. Separate from the script, input and output split
What Should be Created:
Create Log entries
/ Create Script entries
/ Create Detail entries
Create Subset repository
Grouping:
Create a New Script for Each:
Create a New Script for Each:
1 1. One script for everything
2. Connection
3. New combination of (one or more)
Client IP address
Client port
Server IP address
Server port
Protocol
Script Options: (Enter "/" to select)
Suppress timestamps
/ Translate detail data from ASCII to EBCDIC
/ Translate sample data from ASCII to EBCDIC
Split lines at linefeed characters (for readability)
Suppress CONTENT data formatting (DB2C, IMSC, CTG, or ECI)
Script Create Execution Options:
Select Processing Option: (Enter number to select)
X 1. Submit batch job
2. TSO- Enter a slash (/) to select Create Script Filters and display the TCP/IP Script Create screen. See TCP/IP Scripts and Subset Repositories or the online help for information about creating filters.
- Specify the Amount of Data to Use. Performance Test can record any TCP/IP data that passes through and matches your filtering criteria. To record all data, enter ALL in both the Data from Client and Data from Server fields. Otherwise, a non-zero numeric value will limit the amount of data used for Script Creation.
Specify your Script Content options. Script Content fields specify where to store the detail data for your scripts, what to record, and how to process your script data sets.
- Where Should Details be Stored is a required field that specifies where on DASD to store the message details in relationship to your scripts. You must choose one of the options. Enter a number to make your selection:
- Merged into the script places the detail data into the same PDSE member as the script. TCP/IP verbs contained in the script will be merged with the data sent by the verbs. This option allows you to view all data for a connection in a single PDSE member.
- Separate from the script, input and output together places the detail data into a PDSE member that is separate from the script PDSE member. This option keeps the script member uncluttered with (possibly) non-printable data. In addition, a file-formatting tool can be used to display the detail data, since it is now separate from the TCP/IP verbs.
- Separate from the script, input and output split places the detail data into two PDSE members, both of which are separate from the script member. One member contains client data, and the other member contains server data. Client refers to all data sent by the partner that started the TCP/IP connection. Server refers to all data sent by the other partner.
- Specify the What Should be Created options. These options specify what to create from your captured data when requesting script creation processing. Enter a slash (/) to select one or more options.
- Create Log entries generates a Connection Log that lists every script Performance Test for Mainframe Servers created. Each entry consists of a SOCKETS and SCRIPT statement. The SCRIPT statement names the PDSE member containing the TCP/IP connections. The log is written when you issue the Stop or Force line command from the Global Recording Monitor TCP/IP Requests screen. The log, after some modifications, is typically used as the SYSIN data set for your TCP/IP playbacks.
- Create Script entries generates a new script for each TCP/IP connection or for a group of connections. Each script is placed into a different member of a PDSE. The name of each member is also entered into the TCP/IP log on the SCRIPT statement. In this way, the log points to every script that was recorded. A script contains all the TCP/IP verbs (CONNECT, CLIENT, SERVER, etc.) issued by the two partners in each TCP/IP connection.
- Create Detail entries. Details is the term used for the data sent by TCP/IP partners to each other. It might be human-readable or might consist only of binary data. You have a choice of where to store the details:
- Option 1 Recorded with the script member places the details into the same PDSE member as the script; TCP/IP verbs contained in the script will be merged with the data sent by the verbs. This option allows all of the data for a connection to be viewed in a single location: one PDSE member.
- Option 2 Recorded in a separate member places the detail data into a PDSE member that is separate from the script PDSE member. This option keeps the script member uncluttered with (possibly) non-printable data. Also a file formatting tool can be used to display the detail data since it is now separate from the TCP/IP verbs.
- Option 3 Split and recorded in separate members places the detail data into two PDSE members, both of which are different from the script member. One member contains the client data, the other member contains the server data. Client refers to all data sent by the partner that started the TCP/IP connection. Server refers to all data sent by the other partner.
- Create Subset repository generates one or more subset repositories depending on the other selections you make. A subset repository is a filtered copy of the input repository (for example, it contains raw TCP/IP data captured via Global Recording). The filtering is the selection criteria applied by the TCP/IP script creation process.
Accept or change the Grouping fields. Grouping fields control which TCP/IP connections are included in any one script. Your choice of grouping options depends on how you intend to play back the scripts.
To reproduce, at playback time, the timing and sequence of all the TCP/IP connections and messages as seen at capture time, you could choose Option 1 (One script for everything). A script created with this option contains multiple TCP/IP connections, and they are played back in the order recorded in the script.
To have all of your TCP/IP connections played back at once, you could choose Option 2 (Connection). A script created with this option contains a single TCP/IP connection, which can be played back independently of other scripts and connections.
The other options enable you to create scripts that contain just the subset of TCP/IP connections that you need. Select Option 3 (New combination of (one or more)) and select one or more of the following:- Client IP address
- Client port
- Server IP address
- Server port
- Protocol.
IPv6 and IPv4 IP address formats are valid for both the Client IP address or Server IP address.
- Enter a slash (/) to select one or more of the desired Script Options:
- Select Suppress timestamps only if you have no plans to play back the scripts. Time stamps appear with every TCP/IP verb in a script and are used during playback to keep scripts synchronized. If you are using scripts as debugging tools rather than for playback, you might want to suppress time stamps to make the scripts more readable.
- Select Translate detail data from ASCII to EBCDIC to make the data within the script more readable. Almost all data flowing between Web browsers and servers is in ASCII; translating it to EBCDIC makes most of the data readable on the mainframe. The data is translated back into ASCII (internally) during playback.
- Select Translate sample data from ASCII to EBCDIC to make the data within the script more readable when you have chosen to store detail data in external files (not within the script). Sample data refers to the single line of detail data written on the CLIENT and SERVER tags within the script. This sample data is not used during playback. It is only present to help you understand what is contained in a script.
- Select Split lines at linefeed characters to show the detail data in a more readable format. Much of the data transferred between Web browsers and servers consists of readable lines that end with the ASCII linefeed character (x'0A'). Splitting detail data lines at each linefeed character can help you understand what is contained in the script. Playback is not affected by this option.
- Select Suppress CONTENT data formatting if you do not require tags for specific CONTENT data (associated with DB2C, IMSC, CTG, or ECI) to be created in the script. Suppressing these tags may increase the speed of playback and will decrease the size of the scripts. These tags allow for substitution of CONTENT data during playback and aid in readability, but they are not required.
- Script Create Execution Options specify whether you want background (batch) or foreground processing to be your default. Select 1 (background) or 2 (foreground).
- 1. Submit batch job submits a job for background execution.
2. TSO executes script creation as a foreground task under your TSO session. Your session will remain locked until script creation processing completes.
TCP/IP Global Record/Script Create Defaults - Dataset Settings----------------- TCP/IP Global Record/Script Create Defaults -----------------
Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE'
OPTION ===>
More: +
Output Datasets:
Log:
Dataset Name ===>
Member Prefix ===> (1 - 6 character prefix)
Member Suffix ===> (2 - 7 numeric suffix)
Replace? ===> (Y = Yes, N = No)
Script:
Dataset Name ===> 'PMIJSS0.JMS.SCRIPTS'
Member Prefix ===> DEC22T (1 - 6 character prefix)
Member Suffix ===> (2 - 7 numeric suffix)
Replace? ===> (Y = Yes, N = No)
Combined Detail:
Dataset Name ===>
Member Prefix ===> (1 - 6 character prefix)
Member Suffix ===> (2 - 7 numeric suffix)
DDname ===>
Replace? ===> (Y = Yes, N = No)
Client Detail: Log:
Dataset Name ===>
Member Prefix ===> (1 - 6 character prefix)
Member Suffix ===> (2 - 7 numeric suffix)
DDname ===>
Server detail:
Dataset Name ===>
Member Prefix ===> (1 - 6 character prefix)
Member Suffix ===> (2 - 7 numeric suffix)
DDname ===>
- Several Output Datasets will be created. You can add or change the data set name, member prefix, member suffix, or DDname, if desired.
- Dataset Name: Supply a data set name (without a member name) for each row. The data set names can be fully qualified (enclosed in single quotes) or partially qualified (not in quotes). Partially qualified data set names will be prefixed with your TSO prefix (normally your user ID) at processing time. All data sets must be partitioned data sets extended (PDSE). A regular PDS is not supported. For an HTML event summary, supply the HFS path of where the report is to be written (not in quotes).
- Member Prefix: Supply a member name prefix (one to six characters) for each row marked with an *. This prefix is used (in combination with the suffix) to create complete member names to be stored in your data sets. You should select member name prefixes that make it easy for you to identify the type of data stored in each member. You can supply any prefix that is valid as the start of a PDSE member name. For an HTML event summary, the prefix is used with the suffix to create an .htm file and subdirectory.
- Member Suffix: Supply a member name suffix (one to seven numerals) for each row marked with an *. This suffix is used (in combination with the prefix) to create complete member names to be stored in your data sets. As Performance Test creates new members for each new script, the suffix number is incremented to produce a unique member names.
- DDname: Supply a data definition name (DDname) for each row marked with an * that is also for detail data. The DDname can be from one to eight characters in length. The DDname you supply is written into the script member along with the WebSphere MQ verbs. The DDname enables to find your detail data when you play back the script. You must place the same DDname in the Job Control Language (JCL) used to play back your Performance Test scripts.
- Replace?: Specifies whether the script data set will replace a data set of the same name.
Playback TCP/IP profile defaults
This section specifies the TCP playback profile defaults.
Select option 10 Playback TCP from the Edit Profile screen. The TCP Interactive Playback Defaults screen is displayed.
Edit Profile screen
--------------------------------- Edit Profile --------------------------------
Command ===>
More: +
Primary commands: menu-number, ALL, CANCEL
Line commands: S or / to select options.
Active Profile:
Dataset ===> 'PMIJSS0.JMS.ATV.PROFILE'
Member ===> PROFILE
Description ===> changed description
1 Domain Traveler Recording and Playback defaults
2 APPC Global Record and Script Create settings
3 3270/LU0 Global Record and Script Create settings
4 WebSphere MQ Global Record and Script Create settings
5 TCP/IP Global Record and Script Create settings
6 Playback MQ MQ Playback parameter defaults
7 Playback TCP TCP Playback parameter defaults
8 ATV Manager Test Vehicle defaults
Should changes made elsewhere to Profile values be saved?
Profile Autosave ===> Y (Y = YES, N = NO OR A = ASK)TCP Interactive Playback Defaults screen
---------------------- TCP Interactive Playback Defaults ----------------------
Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE'
OPTION ===>
More: +
Playback Information
Live (/ for live I/O, blank for off-line)
Use REXX
Set REXX Stream Variables
Stop On ===> (End compare report generation after the speci-
fied number of mismatches have been reached.)
Standard Wait Time ===>
Think Time Option
2 1. Play at full speed
2. Think time recorded on script
3. User-specified think time
(HH:MM:SS) ===>
Percent ===>
Reporting Options:
Field Depth ===> (Maximum lines to print in field)
Max Lines per Page ===> (30-9999)
Break ===> (E)ject, (N)ext
Datasets:
Reporting Options:
Field Depth ===> (Maximum lines to print in field)
Max Lines per Page ===> (30-9999)
Break ===> (E)ject, (N)ext
Datasets:
Conversation log:
Dataset Name ===>
Script Dataset:
Dataset Name ===>
Database:
Dataset Name ===>
REXX log:
Dataset Name ===>
Error log:
Dataset Name ===>- Specify your TCP Playback Information.
- In the Live field, enter a slash (/) for interactive playback or leave blank for unattended playback.
- Use REXX sets REXXON or REXXOFF on the Performance Test for Mainframe Servers CONTROL statement. This allows you to use REXX clauses outside of script tags to perform tasks such as replacing recorded application data during playback. For Performance Test for VTAM you can use REXX conditional logic to replace recorded inputs with variable names to dynamically replace input data with unique values during playback. Enter a slash (/) to set REXXON or leave blank to set REXXOFF.
- Set REXX Stream Variables on is specified in the Performance Test for Mainframe Servers and the Performance Test for WebSphere MQ CONTROL statements. This parameter enables the use of the Performance Test for Mainframe Servers predefined REXX variables during playback. The variables return information about the playback. Incorporate them into REXX logic that you add to your scripts to control the way the scripts play back. For example, use them to dynamically replace data in the script during playback. Since this is not necessary for replay, the default value for this parameter is usually set to NO. A slash (/) sets the value to YES.
- In the Stop On field, enter a number to end compare report generation after the specified number of mismatches have been reached.
Specify a Standard Wait Time or enter the number of the Think Time Option you want to select.
- Standard Wait Time is the Think Time for each transaction.
- Select one of the following Think Time Options:
- Play at full speed. Transactions are played back as fast as the system can execute them.
- Think time recorded on script. Think time is simulated using the time recorded on the script.
- User-specified think time. Enter the think time in the desired number of minutes and seconds. Or you can enter a percent. One hundred percent specifies the original think time. Fifty percent specifies one-half the original think time. Seconds is the only required value.
- Select the desired Reporting Options.
- Field Depth specifies the number of lines to print in a field before truncating data. This applies only to Text and CSV reports and allows you to truncate the printing of large fields that may contain up to two gigabytes of data.
- Max lines per Page specifies the maximum number of lines to print on a page. Enter a number between 30 and 9999. This applies only to Text reports. The default is 60.
- Break specifies whether to begin each record on a new page or continue the report on the next line. This is valid if you are using form reports in a Text or HTML format. Select EJECT to begin each record on a new page or NEXT to continue the report on the next line. EJECT is the default.
- Name your Datasets.
- Conversation log Dataset Name — The data set name where you want the conversation log to reside on DASD.
- Script Dataset Name — The location of the scripts you will play back. This is a required field and must refer to an existing data set.
- Database Dataset Name — To report on the playback, enter a name for the reporting database. Data from the playback is collected to this database and used in a future reporting job. This field is only required if “Generate Reporting Job” is selected.
- REXX log Dataset Name — Specifies that the output generated by REXX statements in a script is directed to a SYSOUT or DASD data set, rather than to SYSPRINT. If the specified value is a single character, the REXX log is allocated to a SYSOUT class. The SYSOUT goes to the class specified by the single character. If the value is more than one character, the REXX Log is allocated to a permanent file with the name dataset.Pnnnn, where nnnn is the port number assigned to the terminal. Wildcards (* or ?) can be used to identify where the port number (nnnn) is inserted. A member can also be supplied. By default, REXX output is directed to the SYSPRINT data set.
- Error log Dataset Name — The playback error log is a report that describes any errors that occurred during playback. If this field is left blank, the report will go to SYSOUT=*. Enter a data set name or an hfs path to specify an alternate location.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*