Unattended Playback, Dubbing, and Comparison for 3270 and LU0 Scripts (VTAM)

This section describes unattended playback, dubbing, and comparison available with Performance Test for VTAM for 3270 and LU0 scripts. The EHSBATCH program controls unattended mode processing. EHSBATCH helps you perform stress, regression, volume, and concurrent testing of domain destinations such as CICS and IMS/DC, eliminating the need for the user to enter data and drive the application.

Important

Performance Test for VTAM supports script dubbing, while performing unattended playback, and an unattended comparison function that runs independently of playback.

While playback for LU0 scripts is generally the same as for 3270 scripts, special considerations for playing back LU0 scripts are included in the last topic of this section (see LU0-Special-Considerations-VTAM).

Unattended playback allows you to process multiple scripts running in one or more virtual terminals simultaneously logged on to one or more domain destinations. For example, four terminals can be logged on to CICS41A, and six terminals can be logged on to CICSTEST, each running a series of scripts that exercise the transactions and databases.

Unattended dubbing allows you to dub scripts during an unattended playback. With unattended dubbing, you can combine all scripts for a group into one script or create a dubbed script for each script within a group.

The unattended comparison batch program compares two scripts with the same name, one in the DUBLIB (actual), one in the SYSLIB (expected). Unattended comparison reports are then produced by the ETRMCMPR batch program.

When performing an unattended compare, in addition to the current SYSLIB JCL statement that reads existing members, a separate JCL save statement reads “new” members. The libraries referenced by these two statements can be the same or different. The ddname for the new libraries is the same as that for unattended dubbing. EHSBATCH options are specific to playback and have no bearing on comparison. Performance Test for VTAM ignores multiple executions of the same script via TERM, COUNT, or REPEAT.

For an unattended compare, the Performance Test for VTAM comparison log and exception log are combined into one dataset and a special report is added to the end of the consolidated logs. The report provides the port number, script name, dubbing script name (if available), and number of logical screen comparison exceptions.

Important

A called member must be accessible for a compare, just like an actual playback. Unknown script contents, usually REXX, are passed to the REXX environment for processing. After REXX processing, EHSBATCH manipulates the results. This happens before the distinction between compare and playback is known, so the member must exist for the compare to execute. A compare will fail without access to the subroutines that were used when the expected and actual members were created. The compare will also fail if a script is run through session demo with a call to a member that is not in the script file.

This section provides information about the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*