Using REXX variables (Scripting) vBase

Use REXX variables as input

One of the basic features of using REXX with Performance Test is to replace recorded inputs with variable names to dynamically replace input data with unique values during playback.

The following example replaces the employee number field with a variable named employee_number. You can also add a loop to increment employee_number by 1 on each iteration of the loop.

Original

Modified

It is possible with unattended playback to run one script across multiple terminals. Using variable substitution, you can enter unique input data across the different terminals. For example, you can play back a single script that adds an employee number to the database, while simulating multiple terminals with each terminal entering a unique employee number to the application. To do this, insert a compound variable using PORT as the compound variable extension. In this example, the unattended playback controls are GROUP H01AC054 TERM(4) SUMMARY (*) SCRIPT (TEST1).

Perform file I/O from a script

Reading a file from a Performance Test script is done the same way as reading a file in a stand-alone REXX program (see Retrieving-data-from-external-sources-Scripting). Before you read or write to a file, the file must be allocated. ALLOCATE is a TSO command, so you cannot invoke it from REXX in a Performance Test script. Performance Test does provide its own ALLOCATE command. You can use it by invoking ADDRESS HSCMDS.

External File Contents

Script Contents

Read data from VSAM-GETVSAMR

The command,

retrieves a VSAM record. Four REXX variables are used for this command:

• HS_VSAM_DD
• HS_VSAM_KE
• HS_VSAM_RC
• HS_VSAM_REC

Before issuing this command, set HS_VSAM_DD with the allocated DD name of the VSAM dataset and HS_VSAM_KEY with the key. GETVSAMR sets HS_VSAM_RC as follows:

When HS_VSAM_RC is zero, HS_VSAM_REC will contain the VSAM record that matches the specified HS_VSAM_key.

Analyze application screens

You can code REXX in the script to interrogate screen contents. This information can then be used to make IF/THEN/ELSE decisions, to handle synchronization issues, and as input later in the script (as in data replacement).

Use commands such as POS and SUBSTR against the SCREEN variable to analyze data displayed on the screen. The below figure shows an example of this analysis.

Use logic to control script flow

You can use REXX to control playback. Use conditional logic such as IF/THEN/ELSE structures, DO loops, and SELECT structures to do this.

You can wrap DO/END statements around portions of the script. The above figure shows a DO loop wrapped around the section of the script that adds and deletes the employee information to the application. See the below figure for additional examples.

Use the REXX log

The REXX log allows you to create custom reports to document what happens during script execution.

The REXX log creates a file that contains the results of any SAY statements executed from the script.

To create a REXX log during playback via Performance Test for VTAM’s Domain Traveler, enter the RLOG command on the command line. To create a REXX log during an unattended playback, specify RLOG(??) on the GROUP statement.

The below figures shows a complete 3270 script containing REXX logic that:

• Sends the Enter command (up to 100 times) until the system returns a job complete return code

and

• Reports the return code to the REXX log.

Examples of analysis, using logic and the REXX Log (1 of 6)

Examples of analysis, using logic and the REXX Log (2 of 6)

Examples of analysis, using logic and the REXX Log (3 of 6)

Examples of analysis, using logic and the REXX Log (4 of 6)

Examples of analysis, using logic and the REXX Log (5 of 6)

Examples of analysis, using logic and the REXX Log (6 of 6)