Partitioned screens are particularly useful in certain types of application. For example:
For transactions that produce more output than fits on a single screen, scrolling is an alternative to BMS terminal paging (see Output disposition options: TERMINAL, SET, and PAGING). For example, you can define a partition set that consists of just one partition, where the viewport is the whole screen and the presentation space is the entire buffer. You can write to the entire buffer as a single page, and the operator can scroll through the data using the terminal facilities. Response time is to scrolling requests is very short, because there is no interaction with the host. You are limited to the capacity of the buffer, of course.
You may also want to scroll just part of the screen and use some partitions for fixed data.
Another good use for a partitioned screen is "heads down" data entry, where the operator’s productivity depends on how fast the application can process an input and reopen the keyboard for the next. With a partitioned screen, you can divide the screen into two identical entry screens. The operator fills one, presses Enter, and then fills the second one while the data entry transaction is processing the first input. If the input is good, the program simply erases it in preparation for the next entry; if not, there is still an opportunity for the operator to make corrections without losing subsequent work. The CICS 4.1 Sample Applications Guide contains an example of such a data entry transaction.
In many online operations, the operator sometimes needs to execute a second transaction in order to finish one in progress. Order entry is an example, where the operator may have to look up codes or prices to complete an entry. Many inquiries are similar. The initial inquiry brings back a summary list of hits. The operator selects one and asks for further detail, then may need to select another for detail, and so on. In such cases, a partitioned screen allows the operator to do the second task while keeping the output of the first, which is needed later, on the screen. The CICS 4.1 Sample Applications Guide also contains an example of a lookaside transaction.
"Help" text is still another example of "lookaside". If you allocate one partition of the screen to this text, the operator can get the required tutorial information without losing the main screen.
Applications in which the operator needs to compare two or more sets of data simultaneously are also excellent candidates for a partitioned screen. Partitioning allows a side-by-side comparison, and the scrolling feature makes it possible to compare relatively large documents or records.
If you partition a screen and allocate one area to error messages and other explanatory text, usability is enhanced because the operator always knows where to look for messages, and the main screen areas are never overwritten with such information. CICS® sends its own messages to such a partition if you designate one in your partition set, as we explain in Partition definition.
[[ Contents Previous Page | Next Page Index ]]