5250 Connect User’s Guide
68
Using Other Actions in the 5250 Component Editor
In addition to the Map Screen and Multi Row action, you have all the standard Basic
and Advanced Composer actions at your disposal as well. The complete listing of
Basic Composer Actions can be found in Chapter 7 of the Composer User’s Guide.
Chapter 8 contains a listing of the more Advanced Actions available to you.
Handling Errors and Messages
This section describes common errors you may see while executing the animation
tools.
Screen Field Count Changed
This error occurs during animation or execution of certain transactions. One condition
that can cause this is when a transaction sends one or more screens to the terminal that
do not require a response from the user (i.e., pressing an AID key) and then sends a
screen that does require a response. For instance, some transactions are designed to
display a message screen (e.g., “Please wait...”) and then display the actual transaction
screen that the user wants. The user cannot respond to the message screen, since its
display is under the control of the transaction. The problem with transactions behaving
this way occurs during animation. As you step from action to action, Composer’s Map
Screen actions count how many fields each screen has and compares this number with
the original field count when you recorded the component. Since the transaction can
send a second screen before you have stepped to its corresponding Map Screen action,
the field counts get out of sync.
