The Java User Interface provides a function for schedule (JSCH) tasks called Reload definition at period turnaround.
When you do this, message U04002547 appears:
U04002547 ATTENTION: Active instanc(es) of Schedule 'UC0.ITE.TEST#1_2.JSCH' will be reloaded at the next period turnaround.
The same message appears whenever you save changes to a schedule that has active instances.
The option can be toggled on or off. When this option has been chosen, a check mark appears next to the option in the menu.
Even though it appears one performs this action at the task level, there is some evidence that the function applies to all running instances of the schedule. For example, if you open the schedule object, you’ll see a message like this at the top of the window:
Active instance(s) will be reloaded after period turnaround (00:00).
Also, the the related ReloadNextTurnaround Java API class works on schedule objects, not tasks.
The Reload definition at period turnaround function behaves differently depending on how it is triggered:
U00020736 Schedule runtime modification: Reload was set to 'OFF' !U00020736 Schedule runtime modification: Reload was set to 'ON' !
I have a few questions about the Reload definition at period turnaround function:
Here’s one more detail. When one initiates the Reload definition at period turnaround operation via the Java User Interface, the program sends the following XML to the AE server:
<uc-env clientVersion="12.0.6+build.5885" redlight=" " request="eh_79" session="0000000413898371" useridnr="0001025153"> <request id="SET_RELOAD" idnr="413908838" name="jsch_setreload" src="eh"/></uc-env>
It seems pretty clear that the JUI uses an API that is not public.
I have learned that both the write (W) and modify at runtime (M) authorizations are required to perform the Reload definition at period turnaround operation.
Actually, it’s a bit more complicated. The authorization required to use Reload definition at period turnaround depend on how the function is triggered.
ReloadNextTurnaround API class
All active tasks of schedule
If the same user must be able to perform the action in both the JUI/AWI and via the APIs, the user must have both M and W authorizations.
A few more things to note:
select max(EH_ReloadFlag)from EH left join OH on EH_OH_Idnr = OH_Idnrwhere OH_Name = 'TEST1.JSCH'
The feature is available in AWI v12.0 and later. It has been moved however, compared to where it was in the Java User Interface. It is no longer located in the contextual menu that appears when one right-clicks on a schedule instance in the list of active tasks. Instead, one must open the Schedule Monitor for a schedule instance. First display the list of tasks in the Process Monitoring perspective.
The Schedule Monitor tab for the selected schedule instance should appear.
The Reload definition at period turnaround can be found in the Modify Schedule menu.
When you have enabled this option, a blue informational message will appear at the top of the Schedule Monitor.
Also, a check mark will appear next to the option in the Modify Schedule menu.
See the page Modifying Active Schedules in the AWA v12.2 User Guide.
In the DB, the reload at period turnaround flag is stored in the EH (Activities) table in the column EH_ReloadFlag. This would suggest that it’s task/instance-specific.
select OH_Name, EH_AH_Idnr, EH_ReloadFlagfrom EH left join OHon EH_OH_Idnr = OH_Idnrwhere OH_Name = 'UC0.ITE.TEST#1_2.JSCH'
The Automation Engine really does behave differently depending on how the reload at period turnaround function is triggered.
I confirmed this using the DB query above.
I have no idea why it works this way. My guess is that when the public Java APIs were being finalized:
It does seem like a gap in the APIs though.