Performance Test User Profiles
Performance Test uses profiles to help end-users tailor their view of the product. Since Performance Test is a very flexible product that requires options and parameters to be entered or chosen in many places throughout the program, these profiles make it possible for the Performance Test installer to set options in user profiles at installation time. These profiles are then set for all users when they first enter the product. The benefit is that the product is tailored to your site and how you will use the product. This saves time for both new and advanced users by minimizing the need to learn and remember settings when using the product. Novice users will more quickly become productive in the use of Performance Test. More experienced users will still be able to override the defaults and fine tune Performance Test to their needs.
Viewing or setting profile options
The Performance Test Product Menu displays the name of the current profile for your Performance Test session. The profile sets the default values to be used throughout Performance Test, thus enabling you to minimize the knowledge necessary to take advantage of Performance Test’s many features.
Important considerations
- The screens on your system may not look exactly the same as the screens in this section depending on the defaults that your installer set.
- Some of the screens have a large scrollable area. Be sure to navigate through the panels, using the FORWARD and BACKWARD keys, so you will not miss any fields that may need to be changed. Use the PREV and/or NEXT commands to navigate to the next or previous option when the ALL command was used.
- See the online help for a complete description of the fields and commands for each of the screens described in this section.
- When you update a screen and exit with END, your updates will be retained unless you enter CANCEL on the Performance Test Profile primary screen. CANCEL is also valid on all of the profile sub-panels and returns to the next higher-level panel discarding any changes made on the panel where CANCEL is entered. If you entered ALL in the Performance Test Profile screen or selected multiple sub-panels, CANCEL returns to the Profile screen instead of going to the next panel selected, and all changes made while in the CANCELed Profile screen will be discarded. END entered on any of the sub-panels saves your changes and returns to the Performance Test Profile screen. If the ALL command was entered, END proceeds to the next selected profile option panel.
- If you are running with no profile, and the PF keys have never been set, they will be set to the following:
PF01 = HELP PF04 = RETUR PF07 = UP PF10 = LEFT PA1 = PF17
PF02 = SPLIT PF05 = RFIND PF08 = DOWN PF11 = RIGHT PA2 = PF18
PF03 = END PF06 = RCHAN PF09 = SWAP PF12 = RETRI CLEAR= PF22
- If you enter a profile name and leave the profile data set blank, then data set '<userid>.HIPER.PROFILE' will attempt to be created. If a profile of that name already exists, allocation will fail.
Performance Test will allocate a data set for its own internal use by the Profile function. The default data set name is '<userid>.HIPER.TABLES' and the attributes are FB, RECORD LENGTH 80, BLOCK SIZE 80, PDSE. If this data set naming convention does not follow your site standards, an alternative can be used. Pre-allocate a data set name with the above characteristics and allocate it to DD name HSTABLES before using Profiles. Here is an example CLIST statement:
ALLOC DD(HSTABLES) DSN('OTHER.HIPER.TABLES') SHR REUSE
- You can use any pre-allocated data set as a profile data set with the following requirements:
- Enter a new profile name if the data set is empty.
- File must be a PDS or PDSE.
- LRECL=256.
- Block size=2564.
- RECFM=VB.
- File must be large enough to hold a member for each unique TSO user who will use Performance Test with a Performance Test user profile. The default is (CYL,(1,1)).
- Edit the following parameters in the PARMLIB member for Performance Test: HSCM. (PRODUCT_PROFILE is the name of the site profile.)
PRODUCT_PROFILE='MY.COMPANY.SITE.FILE' /* USER PROF DSN */
DEFAULT_USER_PROFILE='@@@@DFLT' /* USER PROF MEM */ - Copy the member @@@@DFLT from the SQQFSAMP data set into the site profile with any name as long as it:
- contains the data from SQQFSAMP(@@@@DFLT)
- has a member name matching the parameter DEFAULT_USER_PROFILE
- has a member name that will not conflict with the name of any TSO userID.
- If you enter the name of a valid profile data set without a profile name, you will receive a member list of that data set. You can then use COPY to create a new member in that data set or another valid profile data set. You can also SELECT, RENAME, or DELETE members in the listed profile data set.
- You cannot enter the name of the Site Profile Dataset as a personal profile data set. This data set is for Performance Test internal use.
- The Site Profile Dataset will be used to store a user’s current User Profile. All users must have write access to this data set but only through the profile program HSPROF. They should not be able to update the site profile directly.
- It is not necessary to create a new Site Profile Dataset for each new Product Install unless the Dataset Attributes have changed. Compare your existing Site Profile Dataset against the Attributes above to determine if a new Site Profile Dataset is needed.
Select, create, or modify a Profile
To select, create, or modify a profile, select 0
Performance Test
Profiles.
Performance Test - Product Menu screen. ---------------- BMC AMI DevX Performance Test - Product Menu ----------------- .
. Option ===> .
. .
. .
. 0 Profiles Set user profiles .
. 1 VTAM VTAM Application Testing .
. 2 Mainframe Servers SNA/APPC & HTTP Testing .
. 3 WebSphere MQ WebSphere MQ Message Testing .
. 4 ATV Manager Automated Testing Vehicle Manager .
. .
. Profile ===> PROFILE .
. Profile dataset ===> 'PMIJSS0.JMS.ATV.PROFILE' .
. .
. Leave Profile blank for selection list .
. Leave Profile dataset blank to create new dataset .
. Leave both blank to run with no Profile .The Performance Test Profile screen appears displaying the profile that was listed on the Performance Test Product Menu.
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) .
. .
. Should changes made elsewhere to dataset names be saved? .
. DSN Autosave ===> (Y = YES, N = NO) .
. .- You can view or update this profile or select another profile to view or update. To view or change a profile other than the one listed, return to the Performance Test Main Menu and enter another profile name. To see a list of available profiles, type an asterisk (*) in the Profile field and clear the Profile dataset field. Type 0 (zero) on the Option line and press Enter.
Options 1 through 11 open screens that let you set the defaults for the currently selected profile. Select the profile options that you want to view or change.
There are several ways to select a profile option:- Enter the option number (1 - 11) on the OPTION line to select the desired option.
- Select one or more options with the S or / line command.
- Enter ALL on the command line, and press Enter. The first option, Domain Traveler, will appear. Make your changes, and press END to step through the rest of the options in sequence.
Profile options include:
- 1 Domain Traveler: Record and playback defaults. For details, see Option 1 – Domain Traveler.
- 2 APPC: Record and script create defaults. For details, see Option 2 – APPC.
- 3 3270/LU0: Record and script create defaults. For details, see Option 3 – 3270/LU0.
- 4 WebSphere MQ: Record and script create defaults. For details, see Option 4 - WebSphere MQ.
- 5 TCP/IP: Record and script create defaults. For details, see Option 5 - TCP/IP.
- 6 Playback MQ: Playback MQ parameter defaults. For details, see Option 6 – Playback MQ.
- 7 Playback TCP: Playback parameter defaults. For details, see Option 7 – Playback TCP.
- 8 ATV Manager: Automated Testing Vehicle Manager defaults. For details, see Option 8 – ATV Manager.
- Select whether you want Performance Test to update your profile when you make changes to profile variables elsewhere in the product. Choices are Y (yes), N (no) or A (ask).
- Select whether you want Performance Test to save changes to data set names that you make elsewhere in the product. Choices are Y (yes) or N (no). Yes allows a repository data set created in Global Recording to become the default in Script Create.
- Enter an e-mail address, if desired. This e-mail address will be used by both the Automated Testing Vehicle (ATV) and Performance Test. For the ATV, the e-mail address is used as the initial value for report distribution for test case run notification. For Performance Test, an e-mail will be sent notifying the user of the status of either a search or queued search request if this field is specified.
- The Codepage field displays the name of the codepage for the data on the client. This parameter is utilized by both reporting and Performance Test. The primary purpose of this parameter is to indicate the client codepage for conversion of data between the mainframe and the client. If you want to use a different codepage, enter it in the Codepage field.
Option 1 – Domain Traveler
Domain Traveler provides an interactive connection from ISPF to the application or subsystem you are testing. Use it to record your activity, play back recorded scripts, compare recorded scripts to live activity, and dub new testing scripts.
Select option 1 Domain Traveler from the Performance Test Profile screen.
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) .
. .
. Should changes made elsewhere to dataset names be saved? .
. DSN Autosave ===> (Y = YES, N = NO) .
. .The Domain Traveler Defaults screen appears.
Domain Traveler Defaults - Session Options and PF Key Translations
. -------------------------- Domain Traveler Defaults -------------------------- .
. Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE' .
. OPTION ===> .
. More: + .
. Default Domain ===> A13TSO (Recording Domain) .
. .
. Session Options .
. Logon Data ===> .
. ZOOM Mode ===> N (Y=Yes, N=No) .
. ZOOM Key ===> F23 .
. LU Name ===> (Terminal name used to login to application) .
. Logmode ===> SNX32705 (Overrides model, SNA and Queriable options) .
. 3270 Model ===> 5 (1=12x40, 2=24x80, 3=32x80, 4=43x80, 5=27x132) .
. SNA ===> Y (Y=Yes, N=No) .
. Queriable ===> Y (Y=Yes, N=No) .
. Trailing Blanks ===> 1 (1 = Single, Y = Keep all, N = Keep none) .
. Infirst ===> Y (Y = No Welcome Screen From Domain Dest.) .
. DBCS ===> N (Y = support DBCS) .
. Edit Application .
. Profiling ===> (/ to edit Application Profiling) .
. .
. The following PF key translations apply to the Domain Destination when .
. in non-Zoom mode: .
. PF01 = F1 PF04 = F4 PF07 = F7 PF10 = F10 PA1 = .
. PF02 = F2 PF05 = F5 PF08 = F8 PF11 = F11 PA2 = .
. PF03 = F3 PF06 = F6 PF09 = F9 PF12 = F12 CLEAR= .- Default Domain allows you to stay within ISPF and access Domain Destinations such as CICS, IMS/DC regions, etc. under which your business applications are run. Enter the desired default domain.
- The Domain Traveler Session Options are fairly straightforward. Fill in or change the desired fields.
- Logon data, if entered, will be supplied to the Domain Destination with your connection request.
- ZOOM mode. In non-Zoom mode, ISPF fills all fields with trailing blanks. Enter Y to initiate session in ZOOM mode and save all trailing blanks, N to initiate session in ISPF mode and remove all trailing blanks, or 1 to remove all but one trailing blank.
- ZOOM key specifies the key that will toggle between ZOOM and ISPF modes.
- LU name is the LU (terminal name) used when establishing a session with the application.
- Logmode describes the characteristics of the terminal (for example, rows and columns) when establishing a session with the Domain Destination. This entry must be defined to VTAM.
- 3270 model describes the type of 3270 device.
- SNA specifies whether Performance Test is emulating an SNA device.
- Queriable specifies whether Performance Test is emulating a queriable device.
- Trailing Blanks specifies whether Performance Test will save or remove trailing blanks. Y will keep all trailing blanks, N will remove all trailing blanks, and 1 will keep one trailing blank.
- Infirst specifies whether to provide a welcome screen from the domain destination. Y prevents the welcome screen from appearing.
- DBCS. Select Y to support double-byte character sets.
- Edit Application Profiling. Enter a (/) to view or modify your Edit Application Profiling settings. Application Profiling examines components of each datastream received from the application and compares it against previously received datastreams to better anticipate the next action the application will take (for example, to send more data or wait for input).
The default PF key translations apply to the Domain Destination when in non-Zoom mode. Make changes if desired.
PF01 = F1 PF04 = F4 PF07 = F7 PF10 = F10 PA1 =
PF02 = F2 PF05 = F5 PF08 = F8 PF11 = F11 PA2 =
PF03 = F3 PF06 = F6 PF09 = F9 PF12 = F12 CLEAR=
Remainder of Domain Traveler Defaults. -------------------------- Domain Traveler Defaults -------------------------- .
. Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE' .
. OPTION ===> .
. More: - + .
. PF03 = F3 PF06 = F6 PF09 = F9 PF12 = F12 CLEAR= .
. .
. Recording Parameters: .
. Script Dataset ===> 'VP.CMU.QQF172.INSTALL3' .
. Replace Members? ===> Y (Y=Yes, N=No) .
. Format Recording ===> Y (Y=Yes, N=No) .
. Record Inputs .
. Only? ===> N (Y=Yes, N=No) .
. Script Recovery ===> Y (Y=Yes, N=No) .
. Input Fields ===> Y (in row,column format? Y or N) .
. .
. Playback Parameters: .
. Repetition Count ===> 1 (1 to 999) .
. Zoom Mode ===> N (Y)es, (N)o, (R)esume .
. Dubbing ===> N (Y)es, (N)o, (C)hange only .
. Suppress Play .
. Screens ===> N (Y=Yes, N=No) .
. Stop Play ===> (Y=Yes, N=No) .
. Play/Think Time ===> 1 ( 1. Play interactively, .
. 2. Play at full speed, .
. 3. Play at think time recorded on script, .
. 4. Play at user specified think time) .
. .
. Identify inputs whose processing should be delayed: .
. ===> .
. Think Time .
. Seconds ===> 01 (If Play/Think Time .
. Hundredths ===> 50 option 4 selected) .
. Percentage ===> 100 (If Play/Think Time is 3 or 4) .
. .
. Comparison Options ===> 4 (1. Any compare check .
. 2. Alpha character differences .
. 3. Field number mis-matches .
. 4. Ignore all compare differences) .
. .
. Initial Mismatch ===> DELTA (ACTUAL,DIFFER, or DELTA) .
. .
. Ignore Numeric .
. Differences ===> N (Y=Yes, N=No) .
. Compare Last .
. Image Only ===> N (Y=Yes, N=No) .
. Dub Encrypted Masks .
. as Character .
. Masks ===> Y (Y=Yes, N=No) .- Fill in or change the Recording Parameters fields.
- Script dataset specifies where you want to store created scripts on DASD. This must be a fully qualified data set name up to 44 characters and defined as a PDS or PDSE. If the data set does not exist, you will be prompted to allocate it.
- Replace Members? Enter Y to replace existing scripts with dubbed scripts.
- Format Recording specifies whether to create a formatted script. Enter a Y to create a formatted script.
- Record Inputs Only? Enter a Y to record only the input entries. If selected, screen images will not be recorded. Enter an N to also record screen images.
- Script Recovery specifies whether to use script recovery. Enter a Y to use script recovery.
- Input fields specifies whether to record the physical row and column of the input rather than the relative input number. Enter a Y to record the physical row and column.
Fill in or change the Playback Parameters fields.
- Repetition Count specifies the number of times to repeat. Enter 1 to 999.
- Zoom Mode specifies whether the script will play in zoom or non-zoom mode. Enter Y for zoom mode, N for non-zoom mode, and R to play the script in zoom mode, but return to non-zoom mode when the script is finished.
- Dubbing allows you to record a new script during the play process.
- Enter Y to invoke the Standard Recording Setup screen. This activates the normal recording mode. The status line will change to indicate that recording is active.
or - Enter C to invoke the change-only Recording Setup screen during execution setup. This activates a background recording that is only saved if the original script encounters a comparison check. The status line is not changed.
- Enter Y to invoke the Standard Recording Setup screen. This activates the normal recording mode. The status line will change to indicate that recording is active.
- Suppress Play Screens:
- Enter Y to invoke the standard Recording Setup screen. This will activate the normal recording mode. The status line will change to indicate that recording is active.
- Enter C to invoke the change-only Recording Setup screen. This will activate a background recording that will only be saved if the original script encounters a comparison check. The status line is not changed.
- Stop Play: Enter Y to halt activity during playback.
- Play/Think Time specifies the think time to be used during playback. The options include:
1. Play interactively: Playback pauses before each screen of data is sent to the Domain Destination.
2. Play at full speed: Transactions are played back as fast as the system can execute them.
3. Play at Think Time recorded on script: Think time is simulated using the time recorded on the script.
4. Play at user specified think time: Think time for all transactions will be the time specified in the “Time (ss th)=>” field.
- Identify inputs whose processing should be delayed: Enter a range of <INPUT> groups whose playback should be delayed. Use this option when the application takes an unusually long time to build the screen into which the <INPUT> group is placed. Only use this field if prior playbacks failed because Performance Test processed these particular <INPUT> groups too quickly.
- Think Time (when option 4 is selected): The Think Time for each transaction specified in seconds, tenths, and hundredths of a second. For example, “00 75" specifies 3/4 of a second think time.
- Percentage applies a percentage figure to the Think Time. This option is applicable when the Play/Think Time is set to 3 or 4. For example to play back a script with half the original think time, enter Play/Think Time ===> 3 and Percentage ===> 50.
Fill in or change the Comparison Options fields.
- The Stop/Mark Comparison Option (COPT) specifies an unattended comparison option that is effective only when used in conjunction with the LOG or XLOG parameters. Choices include:
1. Any compare check: Mark all comparison checks in the log.
2. Alpha character differences: Mark only alpha character differences. Ignore differences in screen attribute bytes.
3. Field number mismatches: Mark comparison checks only if there is a difference in the number of fields on the received and expected screens.
4. Ignore all compare differences: Ignore all comparison checks.
- Initial mismatch specifies which screen is to be placed when a mismatch is detected.
- ACTUAL$: The ACTUAL screen displays the contents of the buffer that Performance Test received from the application.
- DELTA $: The DELTA screen displays an overlay of the position that is different from the actual screen versus the expected screen.
- DIFFER$: The DIFFER screen displays an overlay of the differences between the actual screen versus the expected screen. This overlay is on top on the ACTUAL screen.
Ignore numeric differences (IGND) specifies that numeric values will not be considered when testing for comparison checks. The IGND keyword is only in effect when used in conjunction with the LOG or XLOG parameters. Performance Test considers the following conditions as matching:
- Actual character and expected character are both numeric.
- Actual character is numeric and the expected character is blank or null.
- Actual character is blank or null and the expected character is numeric.
All other conditions are mismatches.
- Compare last image only compares the scripted screen image and the screen image received from the application only after the application has sent all data required to build the final screen. For example, many applications send a map filled with data followed by a map containing only a message. Enter a slash (/) in this field to eliminate comparison of the first data only map but to allow comparison when the full screen image is built from both the data and the message maps.
- Dub encrypted masks as character masks dubs encrypted masks (<MSK>NNN tags) in the script being played back to the new script as both encrypted masks and as an additional record of “I” character masks when you select Y. Select N to prevent additional character masks from being added to your dubbed script.
- Use encrypted masks during compare to prevent miscompares on dark fields. Deselect this option to disable encrypted masks and allow identification of miscompares within dark fields. Deselecting this option does not cause data within dark fields to appear on Actual/Expected screens. This option affects only encrypted masks. All other forms of masking are still valid and in effect for dark fields.
- Identify inputs whose compare processing should be bypassed bypasses compare processing for <OUTPUT> groups that fall within the specified range. For example, enter 1-3,6,77 to bypass compare processing for <OUTPUT> groups 0000001, 0000002, 0000003, 0000006, and 0000077.
- Fill in or change the Auto Documentation Parameters fields.
- Dataset name specifies whether the output generated by the AutoDoc facility is directed to a SYSOUT class or DASD data set. If you enter a single character, the documentation produced by the AutoDoc feature is allocated to a SYSOUT class. If you enter more than one character, the documentation is allocated to a data set file.
- File Format specifies the AutoDoc format that will be generated in standard print formatting and carriage control (PCC), Document Composition Facility script (DCF), or neither of these formats. Enter 1 (PCC), 2 (DCF), or 3 (NONE).
- Record can produce AutoDoc documentation for the output images, screen images with the entered input, or both. Enter 1 (output screens), 2 (input data with output), or 3 (both).
- Screens “boxed” produces documentation with or without borders. Enter Y to produce documentation with borders or N for no borders.
- Running Title specifies the title that will appear at the top of each page. You can use up to 57 characters.
- Fill in or change the Other Datasets fields.
- Journal Dataset specifies that a transaction journal will be generated for the 3270 group. If the specified value is a single character, the journal is allocated to a SYSOUT class. The SYSOUT goes to the class specified by that character. If the value is more than one character, the transaction journal is allocated to a permanent file with that data set name. By default, no transaction journal report is produced.
- Log Dataset specifies that a comparison log for each terminal in the group will be allocated. If the specified value is a single character, the comparison log is allocated to a SYSOUT data set. The SYSOUT data set is in the class specified by that character. If the value is more than one character, the comparison 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 for the port number (nnnn). A member can also be supplied.
Option 2 – APPC
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 of your field values will be recorded. The fields are logically linked together using 'AND'.
Select option 2 APPC from the following Performance Test Profile screen. The APPC Record and Script Create Defaults screen is displayed.
Performance Test 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) .
. .
. Should changes made elsewhere to dataset names be saved? .
. DSN Autosave ===> (Y = YES, N = NO) .
. .APPC Record and Script Create Defaults - Record Settings screen
. -------------------- APPC Record and Script Create Defaults ------------------- .
. 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 .- 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 screen
. -------------------- APPC Record and Script Create Defaults ------------------- .
. Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE' .
. OPTION ===> .
. More: - + .
. / Suspend Script Creation .
. / FORCE Request at 'End Time' .
. Normal Event Notification .
. Error Event Notification .
. .
. -----------------------------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 .
. / 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 ===> .
. Prefix ===> (1 - 6 character prefix) .
. Suffix ===> 0000000 (2 - 7 numeric suffix) .
. DDname ===> .
. .
. Outbound Detail ===> .
. Prefix ===> (1 - 6 character prefix) .
. Suffix ===> 0000000 (2 - 7 numeric suffix) .
. DDname ===> .
. Replace? ===> (Y = Yes, N = No) .
. .
. Inbound 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.
1. 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.
2. 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.
3. 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.
- 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.
- 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 datas et 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.
Option 3 – 3270/LU0
The 3270/LU0 - Record and Script Create Defaults screen specifies the Terminal LU, Applid, and/or UserID you want to record.
Select option 3 3270/LU0 from the following Performance TestProfile screen. The 3270/LU0 Record and Script Create Defaults screen appears.
Performance Test 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) .
. .
. Should changes made elsewhere to dataset names be saved? .
. DSN Autosave ===> (Y = YES, N = NO) .
. .3270/LU0 Record and Script Create Defaults screen
. ------------------ 3270/LU0 Record and Script Create Defaults ----------------- .
. Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE' .
. OPTION ===> .
. More: + .
. --------------------------------Record Settings-------------------------------- .
. Message Filters ("/" for Filter panel) .
. .
. Capture Criteria: .
. Terminal ===> * Use an asterisk for wildcarding .
. Application ===> * the Terminal, Application or Userid .
. User ID ===> * fields. .
. OR .
. Global Record Manager List ===> select to edit list .
. Second Filter GRM List ===> select to edit list .
. .
. 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 ===> 00 : 00 : 00 End Date 00 / 00 / 00 .
. .
. Repository Dataset: .
. Dataset Name ===> 'PMIJSS0.EXAMPLE.REPOS*' .
. First Number ===> 1 (if wildcard in dataset) .
. Last Number ===> 5 (if wildcard in dataset) .
. Replace or Append ===> 1 (1 = Replace, 2 = Append) .
. .
. Recording Options: (Enter "/" to select) .
. Suspend Script Creation .
. / Re-use Repositories .
. FORCE Request at 'End Time' .
. / Normal Event Notification .
. / Error Event Notification .
. Record From LOGON Only .
. .
. -----------------------------Script Create Settings---------------------------- .
. Script Dataset: .
. Dataset Name ===> 'PMIJSS0.JMS.SCRIPTS' .
. Description ===> SMOKE TEST VTAM DEC2022 .
. Member Prefix ===> DEC22 (1 - 6 character prefix) .
. Member Suffix ===> (2 - 7 numeric suffix) .
. Session Log ===> (1 - 8 character member name) .
. Replace? ===> (/ = Yes, Blank = No) .
. .
. Script Format Options: (Enter "/" to select) .
. / Format the Recording Blank to generate unformatted .
. Input Only Blank to capture input and output .
. / Input Field Formats Change Input Fields to Row/Column Format .
. .
. Message Filtering Options: (Enter "/" to select) .
. Use Message Filters (Use REXX Scripts) .
. I Filter Default (I = Include, E = Exclude) .
. .
. Script Create Execution Options: .
. Select Processing Option: (Enter number to select) .
. 1 1. Submit Batch Job .
. 2. TSO .
. .- Entering a slash (/) to select Message Filters displays the 3270/LU0 - Message Filters screen. See the Performance Test for VTAM User space or the online help for information about creating these filters.
The Capture Criteria fields specify what you want to capture. Fill in the Terminal, Application, and/or User ID fields or the Global Record Manager List field.
- Terminal specifies the logical unit (LU) name of the VTAM terminal to record.
- Application specifies the ID of the VTAM application to record.
- User ID specifies the mainframe User ID to capture.
For Terminal and Application, you can enter a fully-qualified 8-character name. For User IDs you can enter a fully-qualified 7-character name. You can also use a wildcard (*) to capture all terminals, Applids, and User IDs—or you can specify a group of terminals, Applids, and User IDs starting with the same prefix (for example, TEST*).
If you prefer, you can specify a Global Record Manager List and, optionally, a Second filter GRM List instead of the Terminal, Application, and User ID fields. These fields can only be specified if the Terminal, Application, and User ID fields are left blank.
- Global Record Manager List and Second Filter GRM List specify the name of a Global Record Manager INCLUDE or EXCLUDE list. If you specify a list that does not exist, when the user reaches this point in the record process, the Global Record Manager * Add List screen will appear to allow the user to create the list before the capture criteria is accepted. To use the Second Filter GRM List, you must first have specified the Global Record Manager List. The second filter will be applied to the result of the first filter.
- 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.
- Question mark (?): Inserts the incremented value into the data set name qualifier where the question marks appear. Enter at least one question mark for each digit of the greatest value in the range fields. For example, USER.#3270.REC?? with first=9 and last=11 creates the following capture repositories:
USER.#3270.REC09
USER.#3270.REC10
USER.#3270.REC11
- Question mark (?): Inserts the incremented value into the data set name qualifier where the question marks appear. Enter at least one question mark for each digit of the greatest value in the range fields. For example, USER.#3270.REC?? with first=9 and last=11 creates the following capture repositories:
- Repository Dataset specifies the name of the data set where captured data will be stored on DASD. You can enter a fully-qualified data set name up to 44 characters in this field to allocate a fixed repository. You can also enter a data set name with a wildcard of “*” or “?” that will result in the allocation of a repository set. This set is defined by a range of numbers entered in the First and Last number fields.
Enter the data set name and First Number and Last Number fields, if required.Asterisk (*): Inserts an incremented value into the data set name qualifier in which the asterisk appears. This wildcard pads the incremented value with enough zeros to ensure an eight-character qualifier. For example, USER.#3270.REC* with first=1 and last=3 creates capture the following repositories:
USER.#3270.REC00001
USER.#3270.REC00002
USER.#3270.REC00003- First Number and Last Number define the range for wildcard characters entered in the Repository Dataset field. You can enter any range from 0 to 9999999. These fields are required only if you enter a wildcard in the repository data set name.
- Replace or Append specifies whether the captured data will be appended to a data set of the same name or replace it. Enter 1 to replace or 2 to append.
Recording Options control the way your capture request will generate scripts, process the repository, stop your requests, send normal and/or error messages, and capture in-flight session data.
Enter a slash (/) to select an option.- Suspend Script Creation controls automatic script creation. To prevent script creation at the end of the recording request, enter a slash (/) in this field and press Enter. 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. This will also cause automatic script creation to execute when your capture request is stopped.
- Re-use Repositories controls whether repository sets will be reused when the last data set in the sequence is filled. Enter a slash (/) to reuse your repository sets. For example, if you enter a First and Last number of 0000001 through 0000010, when segment number 10 is full, the data recorder will close segment 10 and reopen segment 1 replacing the oldest captured activity with the newest. Leave this field blank to terminate recording when the last segment is full.
- FORCE Request at 'End Time' controls whether your capture request will be forced rather than stopped when it reaches the End Time you specified in your request. FORCE terminates recording of all sessions including in-flight sessions. Script creation begins immediately unless the Suspend script creation option is selected. Be aware that you may lose buffered data, resulting in partially recorded sessions.
If you do not select this option, a STOP command is issued at the request’s specified end time. It stops recording new sessions, but continues to record any active sessions. After all in-flight sessions end, recording terminates and script creation begins unless the Suspend script creation option is selected. Although this ensures complete session captures, it may delay script creation.
This field can only be selected if you entered an End Time in your request.
Enter a slash (/) to select.
- Normal Event Notification and Error Event Notification control whether normal and error event messages are generated and sent to your TSO session. If you are recording a large number of sessions, consider disabling Normal event notification to reduce the number of messages you receive.
Enter a slash (/) to receive these messages at your terminal or leave blank to disable sending messages.
- Record From LOGON Only controls whether to start capturing sessions that are already in flight when the request is started. If you leave this field blank, your capture request will start capturing data for sessions that have already been logged on and meet your capture filter criteria. If you enter a slash (/), your request will only capture sessions that log on after the request is started.
- Specify the Script Create Settings.
- Script Dataset Name, Member Prefix, and Member Suffix specify the fully-qualified data set and member names where you want to store your scripts. Enter a 1-6 character prefix and/or a 2-7 numeric suffix. Enter a Description if desired.
- Session Log specifies the name of the log file for this session. Enter a 1-8 character member name.
- Replace? specifies whether the script data set will replace a data set of the same name. A slash (/) = yes and blank = no.
- Specify the Script Format Options.
- Generate Formatted Script specifies whether formatted or unformatted scripts will be generated. Enter a slash (/) to generate formatted scripts or leave blank to generate unformatted scripts.
- Input Only specifies whether to capture input only or input and output. Enter a slash (/) to capture input only or leave blank to capture input and output.
- Input Field Formats allows you to change input fields to a row/column format. Enter a slash (/) to select.
- Specify the Message Filtering Options. Message Filtering lets you filter the data in your 3270 or LU0 sessions so that only the inputs and outputs you are interested in are stored in the script. You typically use Message Filtering to limit the size of your scripts and to create scripts containing only specific messages or transactions. You write short programs in REXX to tell Performance Test the parts of a session to keep and parts to ignore. REXX programs that you write can examine the screen images and user input that flow during a session. You then set indicators in your REXX programs to identify the screen images and user input Performance Test should keep or ignore. Enter a slash (/) to select.
- Use Message Filters controls the formatting of your scripts. Enter a slash (/) to apply message filters to your captured data during script creation. Leave blank, and message filters will not be used during script creation even if you specified them in the 3270/LU0 - Message Filters screen.
- Filter Default. Enter I to include or E to Exclude.
- Script Create Execution Options specifies whether you want background (batch) or foreground processing to be your default. Sample JCL is provided for a batch job, which you can change if desired. Select one of the following:
- 1 Submit Batch Job (background). If you select this option, you must specify a valid OS JCL jobcard in the Job statement information for batch job field.
- 2 TSO (foreground). This option will execute script creation as a foreground task under your TSO session. Your session will remain locked until script creation processing completes.
Option 4 - WebSphere MQ
Select option 4 WebSphere MQ from the Performance Test Profile screen. The WebSphere MQ 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) .
. .
. Should changes made elsewhere to dataset names be saved? .
. DSN Autosave ===> (Y = YES, N = NO) .
. .WebSphere MQ Record/Script Create Defaults - Record Settings screen
. ------------------ Websphere MQ Record/Script Create Defaults ----------------- .
. Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE' .
. OPTION ===> .
. More: + .
. --------------------------------Record Settings-------------------------------- .
. Create Recording Filters (/ for Filter Create panel) .
. .
. Repository Dataset: .
. Dataset Name ===> 'PMIJSS0.AUTODOC.MQ.REPOS*' .
. First Number ===> 0000001 (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: .
. Message Data from GETs ===> ALL (ALL or number of bytes) .
. Message Data from PUTs ===> ALL (ALL or number of bytes) .- Enter a slash (/) on the Create Recording Filters field to access the WebSphere MQ Data Collect screen where you can change data collection criteria.
- 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 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.
- Reuse Repository Options specifies the way your capture request will process the repository.
- 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 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. This option is only valid when using a repository set.
Amount of Data to Record can record any WebSphere MQ data that passes through this MVS system and matches your filtering criteria. To record all of that data, enter ALL in both the Message Data from GETs and Message Data from PUTs fields. Otherwise, any non-zero numeric value will limit the amount of data recorded from a single message to that number of bytes.
WebSphere MQ Record/Script Create Defaults - Script Create Settings screen. ------------------ Websphere MQ Record/Script Create Defaults ----------------- .
. Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE' .
. OPTION ===> .
. More: + .
. ----------------------------Script Create Settings---------------------------- .
. Create Header Filters (/ for Header Filter Create panel) .
. .
. Repository Dataset: .
. Dataset Name ===> 'PMIJSS0.AUTODOC.MQ.REPOS00*' .
. First Number ===> 1 (if wildcard in dataset) .
. Last Number ===> 2 (if wildcard in dataset) .
. .
. Amount of Data to Use: .
. Data from GETs ===> ALL (ALL/number) .
. Data from PUTs ===> ALL (ALL/number) .
. .
. Grouping: .
. Create a New Script for Each: .
. 1 1. One script for everything .
. 2. New combination of (one or more) .
. Queue manager .
. Connection .
. Object (queue) .
. Jobname .
. Event .
. .
. 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 .
. .
. Script Options: (Enter "/" to select) .
. Suppress Time Stamps in Script .
. / Translate Detail Data from ASCII to EBCDIC .
. / Translate Sample Data from ASCII to EBCDIC .
. Include Default MQAPI Script Tag parameters .
. .
. What Should be Created: .
. / Create Log entries .
. / Create Script entries .
. / Create Detail entries .
. Create Event summary entries in CSV format .
. Create Event summary entries in HTML format .
. Create Subset repository .
. .- Enter a slash (/) to select Create Header Filters and display the WebSphere MQ - Header Filter Create screen. See the online help for more information about that screen.
- 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 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 entered a wildcard in the Repository Dataset name field.
- Amount of Data to Use can record any WebSphere MQ data that passes through this MVS system and matches your filtering criteria. To record all of that data, enter ALL in the Data from GETs and Data from PUTs fields. Otherwise, any non-zero numeric value will limit the amount of data recorded from a single message to that number of bytes.
- The Grouping fields allow you to reproduce, at playback time, the timing and sequence of all of the WebSphere MQ data, as seen at capture time, or create scripts that contain just the subset of WebSphere MQ connections that you need.
- Select option 1 to create one script for everything.
- Select option 2 to group your script information by combining one or more of the choices. Your script choices include collecting the following types of information: Queue manager, Connection, Object (queue), Jobname, and Event.
The Script Content fields let you choose where to store your script contents, specify script options, and specify what should be created. Four types of information can be produced: a log, a script, details, and an event summary.
- Where Should Details be Stored? Enter a number to select. The choices include:
- Merged into the script places the details into the same PDSE member as the script. WebSphere MQ verbs contained in the script will be merged with the data sent by the verbs. This allows viewing of all data in a single location — one PDSE member.
- Separate from script, input and output together places the detail data into a PDSE member that is separate from the script PDSE member. This keeps the script member uncluttered with (possibly) non-printable data. In addition, a file formatting tool can display the detail data since it is now separate from the WebSphere MQ verbs.
- Separate from 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 the PUT data and the other member contains the GET data.
- Enter a slash (/) to select your Script Options. These options include:
- Suppress Time Stamps in Script omits time stamps, making the script easier to browse. Select only if you have no plans to play back the scripts. Time stamps appear with every WebSphere MQ 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.
- Translate Detail Data from ASCII to EBCDIC converts the content of ASCII messages to EBCDIC, making it easier to display and edit detail data in ISPF. This option has no effect on messages already in EBCDIC. Performance Test for WebSphere MQ adds the TRANSLATE=A2E keyword to the script tag to indicate that translation has occurred for a particular message. During playback, these messages are converted back to ASCII.
- Translate Sample Data from ASCII to EBCDIC includes a single line, or sample, of the detail data in the script for reference purposes when you store script and detail data separately. This option converts ASCII sample data, based on the CodedCharSetId field of the MQMD, to EBCDIC. Select this option if you plan to view your scripts in ISPF.
- Include Default MQAPI Script Tag parameters writes your application’s entire MQ API parameter set into the script. Normally, Performance Test for WebSphere MQ saves space in the script by omitting parameters with default settings. Use this option to ensure all parameters are set appropriately.
- What Should be Created? Enter a slash (/) to select one or more of the following:
- Create Log entries — A single WebSphere MQ Log is produced for a recording request that you create. The log contains a list of every script that has been recorded at your request. Each entry in the log consists of an MQGROUP statement and a SCRIPT statement. The SCRIPT statement specifies the PDSE member containing the WebSphere MQ message data. The log, possibly requiring modifications, is typically used as the SYSIN dataset for your WebSphere MQ playback job.
- Create Script entries — A new script is produced for each combination of Queue manager, connection, object, jobname, and/or event as specified previously on the Grouping screen. The name of the member is entered into the WebSphere MQ log on the SCRIPT statement. This allows the log to locate the script members during playback. A script contains all the WebSphere MQ verbs (MQ_CONNECT, MQ_OPEN, MQ_PUT, etc.) issued by the specified WebSphere MQ objects and its partners.
- Create Detail entries — Details refers to data sent to or from WebSphere MQ objects. It can be human-readable or it can consist only of binary data. See the first section (“Where Should Details be Stored?”) under Step 10 above to specify where to store the details.
- Create Event summary entries in CSV format — The Event Summary is a report which contains one record for each PUT or GET. Key information on the Event Summary is the date, time, and the WebSphere MQ object associated with the data. Select this option to store the entries as comma separated values.
- Create Event summary entries in HTML format — The Event Summary is a report which contains one record for each PUT or GET. Key information on the Event Summary is the date, time, and the WebSphere MQ object associated with the data. Select this option to store the entries as hypertext markup language.
- Create Subset repository — Enter a slash (/) to create a subset repository.
WebSphere MQ Record/Script Create Defaults - Output Datasets screen
. ------------------ Websphere MQ Record/Script Create Defaults ----------------- .
. Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE' .
. OPTION ===> .
. More: - + .
. Output Datasets: .
. Conversation Log: .
. Dataset Name ===> 'PMIJSS0.AUTODOC.MQ.LOG' .
. Member Prefix ===> LOG (1 - 6 character prefix) .
. Member Suffix ===> (2 - 7 numeric suffix) .
. Replace ===> (Enter "/" to replace) .
. .
. Script Output Dataset: .
. Dataset Name ===> 'PMIJSS0.AUTODOC.MQ.SCR' .
. Member Prefix ===> SCR (1 - 6 character prefix) .
. Member Suffix ===> (2 - 7 numeric suffix) .
. Replace ===> (Enter "/" to replace) .
. .
. Combined Detail: .
. Dataset Name ===> .
. Member Prefix ===> (1 - 6 character prefix) .
. Member Suffix ===> (2 - 7 numeric suffix) .
. DDname ===> .
. .
. Outbound detail: .
. Dataset Name ===> .
. Member Prefix ===> (1 - 6 character prefix) .
. Member Suffix ===> (2 - 7 numeric suffix) .
. DDname ===> .
. Replace ===> (Enter "/" to replace) .
. .
. Inbound detail: .
. Dataset Name ===> .
. Member Prefix ===> (1 - 6 character prefix) .
. Member Suffix ===> (2 - 7 numeric suffix) .
. DDname ===> .
. .
. Event Summary: .
. Dataset Name ===> .
. Member Prefix ===> (1 - 6 character prefix) .
. Member Suffix ===> (2 - 7 numeric suffix) .
. Replace ===> (Enter "/" to replace) .
. .- Where Should Details be Stored? Enter a number to select. The choices include:
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 sub-directory.
- 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: If you want Performance Test to overwrite existing data in your data sets, select the appropriate Replace options. Otherwise, Performance Test will create new members in your data sets.
WebSphere MQ Record/Script Create Defaults - Script Create Execution Options screen
. ------------------ Websphere MQ Record/Script Create Defaults ----------------- .
. Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE' .
. OPTION ===> .
. .
. Script Create Execution Options: .
. Select Processing Option: (Enter number to select) .
. 1 1. Submit batch job .
. 2. Edit batch job .
. 3. Process in foreground .- Script Create Execution Options specifies whether you want background (batch) or foreground processing to be your default. Select 1 to perform background processing. Select 2 to edit a batch job. Select 3 to process in the foreground. Sample JCL is provided for a batch job, which you can change if desired.
Option 5 - TCP/IP
This section specifies the TCP/IP Global Recording and Script Create defaults.
Select option 5 TCP/IP from the Performance Test Profile screen. The TCP/IP Global Record/Script Create Defaults screen is displayed.
Performance Test 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) .
. .
. Should changes made elsewhere to dataset names be saved? .
. DSN Autosave ===> (Y = YES, N = NO) .
. .TCP/IP Global Record/Script Create Defaults - Record Settings screen
. ----------------- TCP/IP Global Record/Script Create Defaults ----------------- .
. Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE' .
. OPTION ===> .
. More: + .
. --------------------------------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 the Performance Test for Mainframe Servers User space 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 screen. ----------------- TCP/IP Global Record/Script Create Defaults ----------------- .
. Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE' .
. OPTION ===> .
. More: - + .
. 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: .
. 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 the Performance Test for Mainframe Servers User space 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.
- 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:
- 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 dataset 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 screen
. ----------------- 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: .
. 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.
Option 6 – Playback MQ
This section defines the playback WebSphere MQ profile defaults.
Select option 6 Playback MQ from the Performance Test Profile screen. The MQ Interactive Playback Default screen is displayed.
Performance Test 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) .
. .
. Should changes made elsewhere to dataset names be saved? .
. DSN Autosave ===> (Y = YES, N = NO) .
. .MQ Interactive Playback Defaults screen
. ----------------------- MQ 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 ===> 15 .
. .
. Think Time Option .
. 2 1. Play at full speed .
. 2. Think time recorded on script .
. 3. User-specified think time .
. (HH:MM:SS) ===> .
. Percent ===> 100 .
. .
. Reporting Options: .
. Field Depth ===> (Maximum lines to print in field) .
. Max Lines per Page ===> (30-9999, 0 for all) .
. Break ===> E (E)ject, (N)ext .
. .
. Datasets: .
. Conversation log: .
. Dataset Name ===> .
. .
. Script Dataset: .
. Dataset Name ===> 'PMIJSS0.JMS.SCRIPTS.SMKMQ' .
. .
. Database: .
. Dataset Name ===> .
. .
. REXX log: .
. Dataset Name ===> .
. .
. Error log: .
. Dataset Name ===> .
. .- Specify your WebSphere MQ 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 WebSphere MQ 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 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. Use a slash (/) to set the value to YES, or leave blank to set it to NO.
- In the Stop On field, enter a number to end the 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:
a. Play at full speed. Transactions are played back as fast as the system can execute them.
b. Think time recorded on script. Think time is simulated using the time recorded on the script.
c. 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 or zero (0) for all. 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 dataset.
- 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 dataset name or an hfs path to specify an alternate location.
Option 7 – Playback TCP
This section specifies the TCP playback profile defaults.
Select option 7 Playback TCP from the Performance Test Profile screen. The TCP Interactive Playback Defaults screen is displayed.
Performance Test 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) .
. .
. Should changes made elsewhere to dataset names be saved? .
. DSN Autosave ===> (Y = YES, N = NO) .
. .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: .
. 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:
1. Play at full speed. Transactions are played back as fast as the system can execute them.
2. Think time recorded on script. Think time is simulated using the time recorded on the script.
3. 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 dataset, 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 dataset.f
- 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 dataset name or an hfs path to specify an alternate location.
Option 8 – ATV Manager
The attributes in this section are used for the allocation of the ATV database. The ATV database is a KSDS VSAM cluster. The fields are initialized to the values specified in the profile selected for the ATV.
Select option 8 ATV Manager from the Performance TestProfile screen. The ATV Manager Defaults screen is displayed.
Performance TestProfile 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) .
. .
. Should changes made elsewhere to dataset names be saved? .
. DSN Autosave ===> (Y = YES, N = NO) .
. .ATV Manager Defaults - Allocation and Performance Test Settings screen
. ----------------------------- ATV Manager Defaults ---------------------------- .
. Profile: PROFILE Profile Dataset: 'PMIJSS0.JMS.ATV.PROFILE' .
. OPTION ===> .
. More: + .
. ATV Database and Asset Allocation Settings: .
. Specify SMS Class Information: .
. Management ===> .
. Storage ===> .
. Data ===> .
. Space Allocation: Data Component .
. Units ===> (BLKS, TRKS, CYLS, KB, MB, or BYTES) .
. Primary ===> .
. Secondary ===> .
. Space Allocation: Index Component .
. Units ===> (BLKS, TRKS, CYLS, KB, MB, or BYTES) .
. Primary ===> .
. Secondary ===> .
. .
. ATV dataset allocation settings: .
. Management Class . ===> (Blank for default management class) .
. Storage Class . . ===> (Blank for default storage class) .
. Volume Serial . . ===> (Blank for system default volume) .
. Device Type . . . ===> (Generic unit or device address) .
. Data Class . . . . ===> (Blank for default data class) .
. Space Units . . . ===> (BLKS, TRKS, CYLS, KB, MB, or BYTES) .
. Primary Quantity ===> (In above units) .
. Secondary Quant. ===> (In above units) .
. .
. TEST CASE SETTINGS: .
. Indicate Status to Set Upon Execution of this Test Case Step: .
. 1.None (Always pass this test case step) .
. 2.Fail (Indicate test case has failed if return code is within range) .
. 3.Pass (Indicate test case step has passed if return code is within range) .
. .
. Specify Return Code Range: .
. Minimum Return Code ===> .
. Maximum Return Code ===> .
. .
. SETTINGS: .
. ATV Master .
. Index Name ===> .
. ATV High Level .
. Qualifier ===> .
. .
. Profile to Use for Regression Automated Test Vehicles: .
. Name: ===> .
. Dataset: ===> .- Fill in the ATV database and asset allocation settings.
- SMS Class Information:
- Management — The SMS Management Class to be used for data set allocation.
- Storage — The SMS Storage Class to be used for data set allocation.
- Data — The SMS Data Class to be used for data set allocation.
- Space Allocation: Data Component:
- Units — The space allocation unit to be used for the allocation of the data component for this data set.
- Primary — The number of units to be used for the primary space allocation of the data component for this data set.
- Secondary — The number of units to be used for the primary space allocation of the data component for this data set.
- Space Allocation: Index Component:
- Units — The space allocation unit to be used for the allocation of the index component for this data set.
- Primary — The number of units to be used for the primary space allocation of the index component for this data set.
- Secondary — The number of units to be used for the primary space allocation of the index component for this data set.
- ATV Script dataset allocation settings — Set allocation attributes for the ATV script file. The fields are initialized to the values specified in the profile selected for this ATV.
- Management Class — The SMS Management Class to be used for data set allocation.
- Storage Class — The SMS Storage Class to be used for data set allocation.
- Volume Serial — The volume serial of the direct access volume you wish to contain the data set.
- Device Type — The generic unit address for the direct access volume you wish to contain the data set.
- Data Class — The SMS Data Class to be used for data set allocation.
- Space Units — The space allocation unit to be used for the allocation of the data component for this data set.
- Primary Quantity — The number of units to be used for the primary space allocation of the data component for this data set.
- Secondary Quantity — The number of units to be used for the primary space allocation of the data component for this data set.
- SMS Class Information:
- Set your pass/fail test case settings.
The following settings specify the status to set upon execution of this test case step. Enter the number of the setting you want to use.- None: Always Pass this test case step.
- Fail: Indicate test case has failed if return code is within range.
- Pass: Indicate test case step has passed if return code is within range.
- Specify return code range. Set a minimum and maximum return code range.
- Specify SETTINGS:
- Enter the ATV Master Index Name. This indicates the file used as an index for ATV(s) that are created. If not specified, the value of parameter ATV_MASTER_INDEX in HSCM PARMLIB member will be used. To create a new ATV Master Index file, use either the index file created at installation as a model, or use JCL member HSATVJCL in your INSTALL dataset.
- Enter the ATV High Level Qualifier. This indicates the file used as an index for ATV(s) that are created. If not specified, the value of parameter ATV_HIGH_LEVEL_QUALIFIER in HSCM PARMLIB member will be used.
- Enter the Profile Name and Dataset to use for regression Automated Test Vehicles. This value will be suggested as the model profile to copy into your new ATV when creating a regression vehicle. You can override this value when creating an ATV.
- Enter the Profile Name and Dataset to use for performance Automated Test Vehicles. This value will be suggested as the model profile to copy into your new ATV when creating a performance vehicle. You can override this value when creating an ATV.
- Replace Like-named Members on Import specifies that imported scripts will replace script members with identical names. Enter a slash (/) to select.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*