Rather than re-inventing a wheel why not use the Language Environment callable service CEELOCT (get current local date or time) https://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ceea300/clcloct.htm%23clcloct?lang=en
Which should be CICS-friendly. If you have to do it in assembler stop using STCK or STCKE and consider using STCKF which gets a "fuzzy" store clock value because doesn't stop all the other processors with a timer interrupt. Both IMS and DB2 have re-written their code that needs a STCK value but doesn't need it to be guaranteed as unique to use STCKF and have seen some incredible performance improvements. Regards, Dougie On 16 November 2015 at 17:32, Paul Gilmartin < [email protected]> wrote: > On 2015-11-16, at 10:17, Gary Weinhold wrote: > > > Depending on how long the process runs and you're concerned that it will > start before midnight and end after, you could force an EXEC CICS call if > TIME is > 23:59. So there'd be a few higher overhead calls right around > midnight. > > > If there's no activity in that final minute, might the date change be > overlooked? > > Beware leap seconds: some sites set CVTLSO to 0; others to the STP value > that IBM > recommends. In the latter case, ignoring CVTLSO can cause the date to be > wrong > 0.03% of the time (always around midnight), or the time about a half > minute off > always. If your STCK values are archival, you must correct with the value > of > CVTLDTO and CVTLSO in effect at the time of the STCK. (The Principles of > Operation contains tables of the latter.) > > -- gil > -- http://twitter.com/DougieLawson
