Netron Fusion™ and NETRON/CAP® do not require any updates for compliance with these DST changes. Programs written with Netron tools may interact with clock time in three places:

1. In the System Date frame, SDATE.F, and the wrapper frame MDATE.F. SDATE.F queries the host operating system for the current date and time, then reformats it in various ways. MDATE.F takes the date from SDATE and supplies the logic for various kinds of date arithmetic (e.g., tell me the resulting date if I add 30 days to today’s date). MDATE.F performs NO time calculations.
2. Declaration and validation of COBOL host variables for TIME and TIMESTAMP columns in relational databases.
3. GUI form validations. If a data entry field in an interactive form is declared as a time form, then a validation is performed to see if the format is correct, e.g., 10:18 is a valid time, but 36:88 is not a valid time.

In the first two cases, the Netron-generated logic is dependent on the operating system's clock and the RDBMS to obtain the correct time. In the third case, since the user is entering the time into a field, the only thing that the Netron logic checks is whether the input data is in the correct format.

In all cases, no Netron-supplied frame or routine manipulates the system clock or otherwise does any calculations or logic to set up or determine Daylight Saving Time.

Please note that any date or time logic written by your developers, either in SPCs (program source), in programmer-written frames, or in programmer-written subroutines, is outside the scope of control of Netron’s frames and tools, and must be validated as well.

If you have any further questions, please contact us.

By email: This e-mail address is being protected from spambots, you need JavaScript enabled to view it
By telephone:

• 1-800-461-6392 (Canada and USA),
• 416-636-8333 (Outside North America)