Insert Replay (ATV)

1. On the Test Case screen, type R (insert replay) next to an object. The replay will be inserted after the selected object. The Select a 3270 Script screen is displayed in the following figure.
   Select a 3270 Script screen
   

      ----------------------------- Select a 3270 Script ---------------- Row 1 of 3
      Command ===>                                                  Scroll ===> CSR
   
      Line commands:. . (S)elect
   
      ATV Name. . ATVMDOC1    Test Case:. BATREPL     Domain Destination:
      Description VALIDATE SYSIN CONTROL CARD PROCESSING FOR BATCH REPLAY JOB
   
      S Name     TPF      Function Description
      - -------- -------- -------- --------------------------------------------------
        SCRF0004 AA01VS01 COMMON
        S250611  H01AC013 COMMON
        S254228  A13TSO   COMMON    TRY ATV TEST STEP SYMBOL FUNCTIONS
      ******************************* Bottom of data ********************************
2. Select a script by typing S next to a script name on the Select a 3270 Script screen and press Enter.
   1. Whether you want to perform Regression or Performance testing determines the screens that follow. For Regression testing, the Session Replay Settings screen is displayed. Continue with the next section, Regression Vehicle Testing.
   2. For Performance testing, the Add Session Replay screen is displayed. Continue with Performance Vehicle Testing.

Regression Vehicle Testing

Session Replay Settings Screen for Regression Testing

1. Enter the connection information for your replay. The Domain Destination and Logmode fields will be pre-filled with script information if available. See the online help for descriptions of the individual fields if necessary.

2. Select one of the Think Time Options:

   1. 
      
      • 1. Play at full speed: play the transactions as quickly as the system can run them.
      • 2. Think time recorded on script: use the think time recorded on the script.
      • 3. User-specified think time: use think time specified in the Think Time field.

   Think Time (mm,ss): With option 3, you need to specify the think time value for each transaction. Time can be specified in seconds (ss), tenths (t) of a second, and hundredths (h) of a second. For example, 00 75 specifies 3/4 of a second think time.

   Think Time Percent: Applies a percentage figure to the think time. This option is applicable when option 2 or 3 is selected. For example, to play back a script with half the original think time, select option 2 and type 50 in this field.

3. Select one of the Comparison Information options for flagging mismatches during the replay session:
   
   • 1. Flag on any compare check: This option will flag on any compare check. Option 1 is the default.
   • 2. Flag on alpha differences: This option will flag only on alpha mismatches.
   • 3. Flag only on field number mismatches: This option will flag only on field number mismatches.

   • 4. Ignore all compare differences: This option will ignore all compare differences

     Important

     A return code of 8 is set for the replay test step if a mismatch is flagged. This return code can be tested for a Pass/Fail condition.

   • Ignore Numeric Differences: Does not consider numeric values when testing for mismatches.
   • Lastonly: Compares only on the final or compiled screen images set by the application in response to an input. Press Enter to continue and return to the Test Case screen. Your replay will now appear in the object list on the Test Case screen.

Performance Vehicle Testing

Add Session Replay Screen for Performance Testing

The Connection Information fields allow you to specify the Domain Destination the Performance Vehicle will connect to, whether the Domain initiates the session, and how long to wait for a response considering the test is for Region Performance.

1. Enter the Domain Destination for this performance vehicle’s VTAM application. There is no default.
2. Specify (in the Infirst field) whether you want Performance Test to wait for the domain destination to send data before beginning the script playback or initiate playback without waiting for the initial data stream from the domain destination. Enter Y or N. N is the default.
3. Enter a Maximum Wait Time that Performance Test will wait for the completion of any I/O from connected partners before terminating the playback. Enter a time that is greater than or equal to 1/100th of a second.
   The Performance Information fields allow you to specify the number of terminals and the number of times to repeat this entire group of scripts during the performance vehicle execution.
4. In the Terminals to use field, enter the number of terminal connections to simulate during the Performance Vehicle execution. This specifies the number of simultaneous connections the playback will establish during the performance vehicle execution. Valid values are 1 to 700. The default is 1.
5. In the Group Repeat Count field, enter the number of times to run this Replay. This specifies the number of times the performance vehicle will be repeatedly run in a serial manner. Valid values are 1 to 999. The default is 1.
   The Performance Threshold fields allow you to specify the amount of allowable variance each specific measurement field can have before the result is identified as having failed the Performance Vehicle playback.
6. Enter the amount of allowable variance during the performance vehicle playback in the following fields: Allowed CPU Resource Differential, Allowed SRB Resource Differential, and Allowed Service Unit Resource Differential.
   These values apply to the targeted CICS regions specified for the unattended playback. The validation for these thresholds is only calculated if the performance vehicle has control of the CICS regions for the playback. Valid values are 0 to 100 percent. Zero (0) percent identifies that this resource will be bypassed for calculation. Zero is the default.
7. Enter the amount of allowable variance for the Average and Maximum transaction response time it takes for the targeted CICS regions to reply during the performance vehicle playback. Valid values are between 0 and 100 percent. Zero (0) identifies that this resource will be bypassed for calculation. Zero is the default.
   The response times are determined using the Performance Test Summary report, which is generated during script playback.
8. Specify whether to Use Baseline execution to Determine Results. Enter Y if you want to use a previous Baseline execution’s results to determine the Pass/Fail status of the current execution. Enter N to use the values specified under Baseline Comparison Values to determine the Pass/Fail status of subsequent runs. The default is Y.
   If you change the value of this field and press Enter, you will return to the Update Replay Session screen. Enter the primary command (S)ession settings to return to the Add Session Replay screen. The Baseline Comparison fields only appear when they can be used. When Y is selected, the Baseline Comparison fields do not appear on this screen. When N is selected, the Baseline Comparison fields do appear.
   The Baseline Comparison fields allow you to specify the baseline values to use when determining the Pass/Fail status of a Performance Vehicle. These values are normally determined from a baseline execution, however, these fields give the option of bypassing a baseline execution and allowing the values to be determined by the client.
9. When bypassing the use of a baseline execution for performance vehicle validation, specify the values to be used to determine the Pass/Fail status by entering a:
   • CPU Baseline Value: the amount of CPU to use for a baseline value when determining Pass/Fail status. The value is Minutes:Seconds:Thousandths in the format mmmm:ss:tt.
   • SRB Baseline Value: the amount of SRB to use for a baseline value when determining Pass/Fail status. The value is Minutes:Seconds:Thousandths in the format mmmm:ss:tt.
   • Service Unit Baseline Value: the amount of Service Units, in K, to use for a baseline value when determining Pass/Fail status. The value can be up to five numeric characters long.
   • Average Response Baseline Value: the acceptable Average Response Time to use for a baseline value when determining Pass/Fail status for the application being tested. The value is Minutes:Seconds:Thousandths in the format mm:ss:ttt.
   • Maximum Response Baseline Value: the acceptable Maximum Response Time to use for a baseline value when determining Pass/Fail status for the application being tested. The value is Minutes:Seconds:Thousandths in the format mm:ss:ttt.