Run Function › How the Run Function Works

How the Run Function Works

Here's how CA Verify for CICS runs a test stream:

• CA Verify for CICS allocates virtual terminals for all the terminals in the test stream you select, using the logged terminal status information to synchronize the status of the virtual terminal with that of the real terminal used in logging.
  • If the applications being run in a test stream require UserID security, the virtual terminal needs to go through signon processing. See the "Security" chapter in the Installation Guide for details on using automated signon for virtual terminals.
• CA Verify for CICS allocates an original display area, a modified display area, and a current display area for each selected terminal. These display areas represent the original terminal display as it appeared during logging, the original display areas as modified by any rules, and the current display as it would appear if the virtual terminal were real.
• CA Verify for CICS then processes each screen in the test stream as follows:
  • For each input screen, CA Verify for CICS enters the data and sends the data to the application. The input screen updates both the original and current display areas.
  • For each input screen that is affected by a rule, CA Verify for CICS creates an original expected screen showing the effect of the application of the rule.
  • For each output screen, CA Verify for CICS updates the original display area and waits for the corresponding output from the application. When the virtual terminal receives the output, CA Verify for CICS updates the current display area. CA Verify for CICS then compares the two output display areas.

If CA Verify for CICS detects a mismatch, it can:

• Interrupt the run. CA Verify for CICS identifies the differences between the expected and current screens. You can then display all three screens (original, expected, and current), correct the differences, terminate, or continue the run.

  Note: During a run, modeling can only be done on the record that has the mismatch.

• Continue the run. You can elect to save the original, current, and expected screens so the mismatches can be viewed when you subsequently browse or print the test stream.

You determine how CA Verify for CICS will execute the run. For example, you can specify:

• What to do with the output from the run; for example: discard it or save it as a new test stream
• What type of comparison CA Verify for CICS should perform; for example: physical, logical, or screen
• What to do with anticipated changes by designing a ruleset to be used when this test stream is run
• Whether or not the operator should explain a mismatch
• The rate at which input is sent to the application, simulating operator think time