Full Screen Matching versus Partial Screen Matching

For block-oriented terminal protocols (such as 3720 and 5250), you will generally want to use full screen matching. Full screen matching secures a fixed point on a text screen. Partial screen matching is most useful for certain data tables or streaming text environments (such as UNIX.)

For example, in the above screen, "UMich Online Catalog" and "Introduction" in the upper right corner would be an excellent way of matching the introduction screen. If you are on the introduction screen, those text blocks will be in the same section of every time the introduction screen opens.

Partial screen matching is most useful for streaming text environments (such as UNIX) as well as retrieving data from a large table; as shown in the table below:

Partial screen matching occurs on a line basis rather than a screen basis. Match rules created for a Partial screen apply to as many lines that qualify. For example, in the above screen, a match rule that uniquely identifies each line would allow Studio to match separately for every single title and author by book. For automation purposes, instead of creating separate fixed fields for every line and column, you can use partial screen matching to have one match rule that applies to all fourteen lines.


Related information

Text Adapters - Overview

Emulator Adapter Components - Properties, Methods and Events

Host Applications - Property, Method and Event Exceptions by Component Name


Privacy | Trademarks | Terms of Use | Feedback

Updated: 18 June 2020

© 2016 - 2020 Pegasystems Inc.  Cambridge, MA All rights reserved.


OpenSpan data classification label