Hitachi

JP1 Version 12 JP1/Automatic Operation Service Template Developer's Guide 


8.3.24 Displaying a repeated execution flow during debugging

For steps that execute a Repeated Execution Plug-in during debugging, a flow for each iteration is displayed in the level below the Repeated Execution Plug-in. This is called a repeated execution flow. Repeated execution flows appear in the flow area and the Flow Tree area as soon as execution of a Repeated Execution Plug-in starts (and remain displayed during and after execution of the plug-in).

The name of a repeated execution flow is displayed in Step [iteration-number]:input-value-(reserved.loop.input) format. Displayed repeated execution flow names that are 65 characters or longer are truncated after the 64th character. If the Input Properties value contains control characters, the name is truncated after the 64th character after removing the control characters. Note that the iteration-number is a two-digit number.

The following shows an example of a Repeated Execution Plug-in executed when hostA,hostB,hostC is specified for the input property of the Repeated Execution Plug-in (inputProperties). In this example, the displayed flow names are Step[01]:hostA, Step[02]:hostB, and Step[03]:hostC.

Figure 8‒19: Flow display for repeated execution flows

[Figure]

Figure 8‒20: Flow tree view of repeated execution flows

[Figure]

Note that repeated execution flows for all iterations are displayed regardless of whether the repeated execution method is parallel or serial.

However, if you log out during debugging, information about iterations might no longer be displayed for repeated execution flows that are in Waiting for Loop Execution status.

If you set breakpoints for a step in the subordinate flow before executing the Repeated Execution Plug-in, the breakpoint settings are applied to the same step in the repeated execution flow displayed after the processing is performed. If you set or cancel breakpoints for a step in a repeated execution flow after repeated execution flows are displayed, the breakpoint settings are applied to the same step in other repeated execution flows.