Performing 5250 Actions
69
To correct this error, you must determine why the field count has changed and then
try one of the following remedial actions.
Double-click the Map Screen action that failed in the Action Model and
change the field count variable to the correct number of fields.
Double-click the Map Screen action, disable field count checking (see
illustration below), and wrap the whole Map Screen action block within a
Try/OnError action that will allow you to conditionally process a field count
error instead of an exception being thrown, which halts component
execution.
The Navigator Options Dialog allows you to:
Enter the field count (number) for checking purposes. If the field count is
not correct at runtime, an error will occur. Your Try/OnError action (applied
in the previous step) will trap this error.
You MUST remember to re-select this check box before deployment.
Override connection defaults by clicking in the checkbox to allow an
override based on the seconds entered in the Screen Wait field for one
navigation action.
Set an expression that is checked each time a packet is received and
processed
Return to the next step (which may include Screen Field Count check) if the
Screen Evaluation Expression is true.
Disable the Map Screen field count checking and add your own action to
check the field count. You can do this by creating a Throw Fault action that
checks the field count (e.g.,
ScreenDoc.XPath(“count(SCREEN/FIELD)”)>68) needed for your
application. An example is shown below.
Map Screen field count
checking box.
