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.
Implementation differences between JUI & Java API
The Reload definition at period turnaround function behaves differently depending on how it is triggered:
Triggered via a JSCH task in the JUI Activities window
- Initiated at the task level.
- Can be toggled ON or OFF for an individual task. (Whether this applies to just one task is another question.)
- The state of the setting can be seen in the JSCH object, by the presence of the red message described above.
- Causes a message to be written to the Activation log of the JSCH task. E.g.,
U00020736 Schedule runtime modification: Reload was set to 'OFF' !
U00020736 Schedule runtime modification: Reload was set to 'ON' !
Triggered via the ReloadNextTurnaround Java API class
- Initiated at the object level.
- Can only be turned ON. If successful, when the object is saved with SaveObject, the AE will return message U04002547.
- The state of the setting can be retrieved using the isTurnaroundWarning() method of the Schedule class.
- No message is written to the log of the impacted JSCH task(s).
I have a few questions about the Reload definition at period turnaround function:
- Does the function operate at the task level or object level? In other words, if one triggers the function on one schedule in the JUI Activities window, does the change also apply to any other running tasks of the same JSCH?
- The function is implemented differently in the graphical user interfaces (JUI, AWI) compared to the Java APIs. Does it really behave differently in, or is the difference mostly superficial?
- If the function applies to all active instances of a task, why does the JUI give several indications that the function is task-specific? Moreover, is there a reason for the implementation difference?
- Is the function available in the Automic Web Interface? Yes, the function is available in the AWI since v12.