APAR status
Closed as documentation error.
Error description
You can fill out an interval scheduled trigger however you wish, but when you put in the start time you wish for the trigger to start executing, it is ignored and only the interval is retained (thereby executing the schedule immediately upon the next interval). EX. (current time is 13:00): Interval 10 min. Start Time 18:00 Next fire time is 13:10 instead of 18:00 or 18:10
Local fix
APAR to be created; do not use schedules
Problem summary
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * When creating/modifying an interval schedule, the field * * "Start Time" is described in a confusing manner. What this * * field does, is to specify an anchor value that is used to * * calculate the instances of time that the schedule should run * * at. For example, if the current time is 4:50PM, the interval * * is 30 (minutes), and the start time is set to 17:00 * * (5:00PM), then the next occurrence of this interval schedule * * will be at 5PM. However, if the interval is 6 minutes, and * * the start time is 17:00 (current time is still 4:50PM), then * * the next occurrence is going to be 4:54PM. This is * * calculated by starting at 5:00PM (start time or anchor time) * * and moving back by 6 minutes at a time, before moving past * * the current time in reverse order. Therefore, the "start * * time" is used as an anchor value. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
The description for "start time" should be modified to explain what this field does and how it reflects in the calculation. The behavior is working as expected. The description is fixed in UCB 6.1.3.2.
Temporary fix
Comments
APAR Information
APAR number
PI94456
Reported component name
URBANCODE BUILD
Reported component ID
5725P5700
Reported release
612
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-02-28
Closed date
2018-07-02
Last modified date
2018-07-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS8NMD","label":"IBM UrbanCode Build"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"612","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
02 July 2018